V 5.1.1: Update of 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-6965-00, for Version 5.1.1.

Content


Update 1, 08/2012: PM67565 provides updated and new messages that are related to Stored Procedure Monitoring.

Update 2, 08/2012: PM64708 provides the new message KO2O1925W.

Update 3, 09/2012: PM68972 provides the new message KO2Z091E.

Update 4, 11/2012: Addition of new message FPEV1342I.

Update 5, 12/2012: New messages related to the Spreadsheet Input Data Generator (FPEP1000E to FPEP1024E).

Update 6, 01/2013: PM74343 includes an update of message KO2Z665W.

Update 7, 05/2013: PM85113 provides new Background Control messages that are related to long names with variable length.

Update 8, 11/2013: PM99429 provides the new data server message FPEV2737I

Update 9, 02/2014: PM96506 provides the new utility services message FPEU0400W

Update 10, 02/2014: PI05484 provides the new VTAM Display Logic message KO2O1369I

Update 11, 03/2014: PI09778 provides an update of the following messages FPEV0223E and FPEV0114I


*******************************************************************************************************************
Update 11: 03/2014: PI09778 provides an update of the following messages FPEV0223E and FPEV0114I

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.


Message number:
FPEV0114I

Message text:
SERVICE LEVEL IS <V1> APAR <V2>

Explanation:
This message is issued during the startup of the PE Server subtask.
<V1> is the date and the time when the PE Server subtask is compiled.
<V2> is the APAR number of the installed PE Server subtask service level.

User response: None.


*******************************************************************************************************************

Update 10: 02/2014: PI05484 provides the new VTAM Display Logic message KO2O1369I

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 9, 02/2014: PM96506 provides the new utility services message FPEU0400W

Message number:

FPEU0400W

Message text:

MONITORING OF ACCELERATOR VERSION 4 IS NOT FULLY SUPPORTED. REPORTS DO NOT SHOW ALL ACCELERATOR-RELATED COUNTERS.

Explanation:

This version of OMEGAMON XE for DB2 PE does not support DB2 accelerator trace data version 4. Therefore the accelerator information in batch reports, statistics, and record trace does not inlcude all performance-related fields.

User response:

To receive complete information about accelerator monitoring, install the latest version of OMEGAMON XE for DB2 PE.


*******************************************************************************************************************

Update 8, 11/2013: PM99429 provides the new data server message FPEV2737I

Message number:
FPEV2737I

Message text:
<V1> DB2 MESSAGES COLLECTOR TIMEOUT OCCURRED.

Explanation:
A request from a user interface cannot be handled by the Data Server instance because a timeout occurred. The request could not be completed in time.

<V1> is the DB2 subsystem ID.

User response:
Resubmit the request. If the problem persists, contact IBM support.

*******************************************************************************************************************
Update 7, 05/2013: PM85113 provides new Background Control messages that are related to long names with variable length.

Message number:
FPEC4030W

Message text:
IFCID <V1>. DATA SECTION <V2>. REPEATING GROUP <V3>. FIELD <V4> HAS A LENGTH OF <V5>. EXCEEDING THE ALLOWED LENGTH OR EXCEEDING THE DATA SECTION LENGTH <V6>. FIELD <V4> IS IGNORED FROM FURTHER PROCESSING.

Explanation:
For some IFCIDs, DB2 provides long names with variable length.

For a particular data section field, the internal integrity validation for a long string failed. Processing continues assuming that a long name is not provided.

<V1> is the DB2 IFCID number.
<V2> is the name of the data section.
<V3> is the repeating group number of the DB2 data section.
<V4> is the name of the field within the DB2 data section.
<V5> is the value for the length of the long name that is found in the DB2 data section.
<V6> is the value of the length of the DB2 data section.

User response:
Contact IBM Support to validate the data that is supplied by DB2.


Message number:
FPEC4035W

Message text:
MORE THAN <V1> LONG STRINGS QUALIFYING FOR UNIQUE NAME PROCESSING FOUND IN THE INPUT DATA. THIS CAN INDICATE AN INPUT DATA PROBLEM. UNIQUE
NAME PROCESSING HAS BEEN SUSPENDED TO PREVENT PERFORMANCE DEGRADATION.

Explanation:
This message might be displayed in conjunction with message FPEC4030W.

The Batch Reporter program complements a long name with a unique short name to be included in reports and traces. However, if too many pairs of long names and short names are accumulated, the Batch Reporter performance might degrade considerably.

A reasonable number of internally stored unique long names is exceeded. Processing continues, however,
instead of adding unique short names, the long names are truncated and added as short names.

<V1> is the number of internally stored unique long names.

User response:
Contact IBM Support to validate the data that is supplied by DB2.

*******************************************************************************************************************

Update 6, 01/2013: PM74343 includes an update of message KO2Z665W

Message text:

KO2Z665W LPAR=Lparname not connected to service XCF request SSID=Subsystem-ID CBA=Service-request RSN=Reason-code

Explanation:

  • Lparname specifies the remote XCF gateway target LPAR.
  • Subsystem-ID specifies the target DB2 subsystem.
  • Service-request specifies the remote control block access request routine
  • Reason-code is RSN=0000 1292 for version 5.1.0 or RSN=0000 1396 for version 5.1.1

A member of the XCF-gateway sent a request to a member (LPAR) that resides on a remote XCF-gateway. The member on the remote XCF-gateway is not yet fully initialized, or it does not exist. Therefore DB2 subsystem monitoring data cannot be exchanged with the specified remote XCF gateway.

User response:

Verify that the remote XCF-Gateway LPAR is successfully initialized and connected. Restart the request.


*******************************************************************************************************************
Update 5, 12/2012: New messages related to the Spreadsheet Input Data Generator (FPEP1000E to FPEP1024E)

The messages from FPEP1000E to FPEP1024E are related to the Spreadsheet Data Generator.

ko2me_fpep.pdfko2me_fpep.pdf


*******************************************************************************************************************

Update 4, 11/2012: Addition of new message FPEV1342I

Message text:

FPEV1342I MSTR EXCLUDEDDB2SSID=(<V1>)

Explanation:

This message is displayed during the startup of the PE Server subtask controller (MSTR) and in response to a DISPLAY command.

<V1> is the list of comma separated DB2 subsystem IDs.

A listed DB2 subsystem can be excluded from being monitored because of the following reasons:

  • During the configuration step, it is specified that the subsystem does not start monitoring.
  • The PE Server subtask controller access to the DB2 subsystem is denied.
  • The configured DB2 subsystem does not exist or is not supported.
  • A required parameter data set member for the DB2 subsystem does not exist.
  • An error occurred during the preparation or the startup of the monitoring PE Server subtask.

User response:

If the DB2 subsystem is expected to be excluded from being monitored: none.

Otherwise, see the PE Server subtask logs SYSPRINT or JESMSGLG for related error messages, correct the error, and restart the OMEGAMON Collector started task.

*******************************************************************************************************************
Update 3, 09/2012: PM68972 provides the new message KO2Z091E.

Message text:
KO2Z091E OMPE Vnnn Collector address space is terminating due to PESERVER failure.

Explanation:
The PESERVER subtask failed. It cannot be restarted due to serveral ABENDS.

System action:
The OMEGAMON Collector address space is terminated.

User response:
Restart the OMEGAMON Collector address space. If the failure persists, contact IBM Support.


*******************************************************************************************************************

Update 2, 08/2012: PM64708 provides the new message KO2O1925W.

Message text:
THE AUTHORIZATION EXIT IS ACTIVE. ALL DATA IS SUPPRESSED.

Explanation:
The parameter USEUSERAUTHEXIT=Y is configured. The authorization user exit is active.

System action:
This parameter is specified in the <HILEV>.RKD2PAR member OMPEMSTR.

User respone:
Contact your administrator.

*******************************************************************************************************************

Update 1, 08/2012: PM67565 provides updated and new messages that are related to Stored Procedure Monitoring.

The messages from FPEV2702I to FPEV2736I are updated or new.

FPEV2702I_FPEV2736I.pdfFPEV2702I_FPEV2736I.pdf


*******************************************************************************************************************

Publication number

GH12-6965-00

Copyright date

1985, 2012

Original publication date

2012/6/15

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 Tools for z/OS

Software version:

5.1.1

Operating system(s):

z/OS

Reference #:

7035918

Modified date:

2014-03-24

Translate my page

Machine Translation

Content navigation