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

Content

Update 1: (October 2015) provides the new OMEGAMON PE Subsystem messages KO2Z958I, KO2Z959I and KO2Z960E

Update 2: (November 2015) provides the new VTAM Display Logic message KO2O1294E

Update 3: (May 2016) provides new Data Server messages FPEV2108E and FPEV2109E and updates to message FPEV0405E

Update 4: (June 2016) provides the new VTAM Display Logic messages KO2O1163E, KO2O1164E and updates to message KO2O1161E to reflect enhanced Application Trace Facility filtering functionality

Update 5: (January 2018) three new informational and error messages: KO2H1407E, KO2H1408W, and KO21409E

Update 5: (January 2018) three new informational and error messages: KO2H1407E, KO2H1408W, and KO21409E:

See the following PDF for details:

ko2me_v530_01102018.pdf

Back to top

Update 4: (June 2016) provides the new VTAM Display Logic messages KO2O1163E, KO2O1164E and updates to message KO2O1161E to reflect enhanced Application Trace Facility filtering functionality

Message number
KO2O1163E

Message text
NO VALUE SPECIFIED FOR FIELD field field1, field2= YES IS NOT VALID

Explanation:
The exclude option field can only be requested if the corresponding value field has one or more values entered.

System action
ATF will not continue trace specification until field(s) have been corrected.

User response
Either enter a value in the filter field, or change the exclude field to N.

---

Message number
KO2O1164E

Message text
XPLN=Y NOT ALLOWED WHEN PLAN=ALL SPECIFIED

Explanation
To exclude plans, you must enter a specific plan name. ALL plans cannot be excluded.

System action
ATF will not continue trace specification until field(s) have been corrected.

User response
Either enter specific plan names instead of ALL or set the XPLN option to N.

---

Message number
KO2O1161E

Message text
MULTIPLE ENTRIES NOT ALLOWED FOR field1 AND field2.

Explanation
You can enter multiple values for the Trace Specification Fields PLANNAME, PACKNAME, COLLID, PKGLOC and AUTHID. However, DB2 TRACE supports the specification of multiple values for only one of the fields.

Back to top

Update 3 (May 2016) provides new Data Server messages FPEV2108E and FPEV2109E and updates to message FPEV0405E

Message number
FPEV2108E

Message text
<V1> DB2 MONITOR PRIVILEGE CHECK USING RACF FAILED FOR USER <V2>

Explanation
If a user interface connects to a PE Server subtask, the PE Server subtask checks whether the user has DB2® MONITOR privilege. This check failed.

<V1> is the DB2 subsystem ID.
<V2> is the user ID.

System action
The PE Server subtask does not support monitoring for the unauthorized user ID.

User response
Grant the user ID or assigned group read access to profile MONITOR1 or MONITOR2.

---

Message number
FPEV2109E

Message text
<V1> DB2 MONITOR PRIVILEGE CHECK USING RACF FAILED FOR USER <V2> (RACROUTE RC=<V3>, RACF RC=<V4> RS=<V5>)

Explanation
If a user interface connects to a PE Server subtask, the PE Server subtask checks whether the user has DB2® MONITOR privilege. This check failed.

The displayed return and reason codes in decimal are obtained from macro RACROUTE, which is called to process the privilege check.

• <V1> is the DB2 subsystem ID.
• <V2> is the user ID.
• <V3> is the RACROUTE return code.
• <V4> is the RACF® return code.
• <V5> is the RACF reason code.

System action
The PE Server subtask does not support monitoring for the specified user ID.

User response
For return and reason codes refer to z/OS® Security Server RACF Macros and Interfaces.

---

Message number
FPEV0405E

Message text
<V1> CONNECTION BY USER <V2> FAILED, NO AUTHORITIES FOUND

Explanation
The user must have MONITOR1 or MONITOR2 privileges to use the online monitor.

If external security (RACF®) is used to secure DB2® resources, the user or assigned group does not have read access for the corresponding profiles. If DB2 internal security is used to secure DB2 resources, no corresponding entry for the user or assigned group exists in SYSIBM.SYSUSERAUTH.

• <V1> is the DB2 subsystem ID.
• <V2> is the user ID.

System action
The PE Server subtask does not support monitoring for the unauthorized user ID.

User response
Grant the required authority to the user or a group the user is assigned to.
Refer to Installation and Configuration.

Back to top

Update 2: (November 2015) provides the new VTAM Display Logic message KO2O1294E

Message number
KO2O1294E

Message text
UNABLE TO USE THREAD EXCEPTION PROFILE %%%%%%%%. PROFILE IS OUTDATED, PLEASE DELETE AND REDEFINE.

Explanation
Exception processing routine found outdated user profile %%%%%%%%.

System action
Exception rules are skipped and processing continues.

User response
Delete and redefine %%%%%%%% user profile.

Back to top

Update 1: (October 2015) provides the new messages KO2Z958I, KO2Z959I and KO2Z960E

Message number
KO2Z958I

Message text
OMPE V530 PE Server RTG service request failed. RC=000C RSN=%%%%%%%

Explanation
The OMPE Collector subsystem was unable to process a common collector request for DB2 performance monitoring data.

• RC=000C - indicates that a severe error occurred processing an initialization function.
• RSN= shows the reason code associated with the error return code.
• RSN=00091228 - OMPE Collector started task address space is not up and running.
• RSN=00091232 - OMPE Collector started task address space not responding.

System action
The Service request for DB2 performance monitoring data is rejected.

User response
Start the OMPE Collector started task address space.

---

Message number
KO2Z959I

Message text
OMPE Vnnn Initialization verification procedures bypassed. EXECIVPS=NO

Explanation
The OMPE Collector subsystem by default, at initialization time, executes the initialization verification procedures. When EXECIVPS=NO is specified, the initialization verification procedures are bypassed.

System action
The initialization verification procedures are not processed.

User response
Specifiy EXECIVPS=YES in RK2DPAR member OMPEOPTS to have the initialization verification procedures executed during OMPE Collector started task address space initialization.

---

Message number
KO2Z960E

Message text
OMPE V530 PE Server environment error. RTG container address not initialized. RC=000C RSN=%%%%%%%

Explanation
The OMPE Collector subsystem was unable to locate the PE Server list of monitored DB2 subsystems.

• RSN=00088544 - PE Server subtask failed to properly initialize.
• RSN=00088548 - PE Server routing table address of DB2 subsystems is not initialized.
• RSN=00088552 - PE Server routing table structure failed validity checks.
• RSN=00088556 - PE Server routing table monitored DB2 subsystem container contains zero entries.
• RSN=00088560 - PE Server routing table monitored DB2 subsystems container contains.

System action
The OMPE Collector subsystem fails to initialize its internal structures that point to the PE Server list of monitored DB2 subsystem. Classic and Common Collector sessions will fail display any monitored DB2 subsystem data.

User responseReview the job log for additional error messages that may have been issued by the PE Server component and verify that the RKD2PAR member OMPEMSTR does not contain validity check errors.

Back to top