V 5.2.0: Update to the Messages manual of IBM Tivoli OMEGAMON XE for DB2 Performance Expert and Performance Monitor on z/OS

Manual


Abstract

This document updates the IBM Tivoli OMEGAMON for DB2 Performance Expert and Performance Monitor on z/OS Messages manual, GH12-6993-00, for Version 5.2.0.

Content

Update 1: PM99292 (December 2013) provides the new VTAM Display Logic messages KO2O1152E, KO2O1169I, and KO2O1167E

Update 2: PI05484 (February 2014) provides the new message VTAM Display Logic message KO2O1369I

Update 3: PI09778 (March 2014) provides an update of message FPEV0223E

Update 4: PI09581 (April 2014) provides an update of the following messages: FPEA0803I and FPEA0804I

Update 5: (July 2014) provides the new message: FPEM229

__________________________________________________________________________

Update 5: (July 2014) provides the new message: FPEM229

Message number:
FPEM229

Message text:
FPEM229 Not all data displayed. Limited support for: <V1>.

Explanation:
Not all data returned by DB2 within IFCIDs are displayed on the Online Monitor panels.

  • <V1> is the reason for the limitation

The following list shows the keywords for the reasons:

Multiple IFCID 2: For buffer pool information DB2 10 returns one or more IFCIDs 2.
Only information from the first IFCID 2 is displayed on the panels. Further IFCIDs 2 are ignored.

User response:
None.


Update 4: Update of the following messages: FPEA0803I and FPEA0804 in PI09581 (April 2014)

Message number:
FPEA0803I

Message text:
THE INPUT TRACE INCLUDES IFCID 233, 380, OR 381 WHICH IS USED TO IDENTIFY A STORED PROCEDURE OR USER-DEFINED FUNCTION MAIN ROUTINE. A REPORT BY ACTNAME TAKES ACCOUNT OF NESTED CALLS BY ACCUMULATING DATA FOR EACH MAIN ROUTINE INCLUDING ITS SUBROUTINES.

Explanation:
IFCID 233, 380, or 381 was found in the input trace and is used for the calculation that is requested by the command ORDER(ACTNAME).
Note :
  • IFCID 380 or 381 is preferred, if available, because it uses less system resources when collecting trace data.
  • Stored Procedures (SP) and User-Defined Functions (UDF) can be identified.
  • Data of subprograms that were called by Stored Procedures or User-Defined Functions are reflected in the output of the main program.
  • The report has a view on data by activity type and name, but not by each package. That is why the following package counters of subprograms are not taken into account:
    1. The occurrence of subprograms
    2. The number of package allocations (switches)
    3. The number of rollup threads
    This approach also affects some package averages.


Message number:
FPEA0804

Message text:
IFCID 233, 380, OR 381 WAS NOT FOUND IN THE INPUT TRACE. THE CALCULATION BY ACTIVITY NAME TREATS SUBPROGRAMS OF A STORED PROCEDURE OR USER-DEFINED FUNCTION AS SEPARATE ACTIVITIES.

Explanation:
The calculation that is requested by the command ORDER(ACTNAME) is limited to the usage of IFCID 3 and IFCID 239. These are the standard Accounting IFCIDs for reporting a thread and a package. The main program of a Stored Procedure or User-Defined Function treats their subprograms as separate activities.

__________________________________________________________________________


Update 3: Updated message FPEV0223E in PI09778 (March 2014)

Message number:
FPEV0223E

Message text:
<V1> RRSAF-IDENTIFY REQUEST FAILED FOR DB2 SUBSYSTEM <V2>. RC= <V3> RS= <V4>

Explanation:
The PE Server issued an RRSAF - 'IDENTIFY' request. This request failed because RRS/MVS was not active or the DB2 subsystem was not attached to RRS/MVS.
<V1> is the originator of the message.
<V2> is the DB2® subsystem ID.
<V3> is the DB2 return code.
<V4> is the DB2 reason code.

User response:

  • If RRS/MVS is not started, start RRS/MVS and restart the OMEGAMON Collector started task.
  • If RRS/MVS is started, restart the OMEGAMON Collector started task or use the MODIFY command to manually start the PE Server subtask for the DB2 subsystem reported in this error message.

__________________________________________________________________________

Update 2: New message KO2O1369I in PI05484 (February 2014)

KO2O1369I - NEAR-TERM HISTORY DATA COLLECTOR - RECORD IS TOO LONG FOR SEQUENTIAL COLLECTION IFCID=<V1> DB2=<V2>

Explanation:
An IFI record length is longer than expected.
<V1> is the name of the IFCID.
<V2> is the name of the DB2 subsystem.

System action:
The record is skipped.
Processing continues with the next record.

User response:
None.

_________________________________________________________________________

Update 1: PM99292 (December 2013) provides the new VTAM Display Logic messages KO2O1152E, KO2O1169I, and KO2O1167E

KO2O1152E THE APPLICATION TRACE START FAILED. THE VSAM DATASET IS FULL.

Explanation:

The application trace cannot be started because the VSAM dataset is full and the option MODE=APPEND is used,

User response:

Use a different VSAM dataset or use the option MODE=REUSE to overwrite existing data in the dataset.

KO2O1167E THE VTAM TRACE CANNOT BE PROCESSED. REASON: <V1> OR <V2>

Explanation:

<V1> TIME OVERLAP OCCURRED

If a deferred trace in ATF is scheduled to write to a particular dataset at a particular time, and you specify another deferred trace to write to this particular dataset at this particular time, this trace cannot be executed because the VSAM dataset is not available.

<V2> MODE=APPEND REQUIRED

If there are one or more deferred traces that write to a particular dataset, and you specify another deferred trace to write to this particular dataset by using the option MODE=REUSE, this trace cannot be started because it would overwrite data from the other traces.

User response:

If <V1> is issued, specify a different dataset or modify the start time or the duration of the trace so that the scheduled time does not overlap with other requests to this dataset.

If <V2> is issued, specify a different dataset or use the option MODE=APPEND.

KO2O1169I THE START DATE IS NOT SPECIFIED. THE CURRENT DATE IS USED.

Explanation:

If the start time is specified without specifying the start date, the current date is used as the start date of the deferred ATF trace.

User response:

None.

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS
IBM Tivoli OMEGAMON XE for DB2 PE / PM / BPA

Software version:

5.2.0

Operating system(s):

z/OS

Reference #:

7040266

Modified date:

2014-07-29

Translate my page

Machine Translation

Content navigation