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

Product documentation


Abstract

This document updates the IBM ® Tivoli® OMEGAMON for DB2® Performance Expert and Performance Monitor on z/OS Messages manual, SC18-9980-00, for Version 4.1.0.

Content

This manual includes the following updates:

  • Update 1: New messages FPEU0011U and FPEU0015I in PK29544 (January 2007)
  • Update 2: Message KO2O1915W provides more information in PK29492 (January 2007)
  • Update 3: New messages FPEV0220W and FPEV0221W in PK27502 (February 2007)
  • Update 4: New messages KO2I0180U, KO2I0204U, and KO2I0212I in PK35988 (May 2007)
  • Update 5: Remark about OBnnnn messages from OMEGAMON base code (May 2007)
  • Update 6: New message KO2O1161E in PK44154 (May 2007)
  • Update 7: Several new and changed messages (June 2007)
  • Update 8: New messages FPEV0266I and FPEV0267I (August 2007)
  • Update 9: New message KO2I0929E in PK50364 (August 2007)
  • Update 10: New messages KO2R136E to KO2R262E in PK44284 (August 2007)
  • Update 11: New messages KO2I0186U to KO2I0213U in PK50388 (October 2007)
  • Update 12: New message KO2R1155I in PK56009 (January 2008)
  • Update 13: Correction of messages FPEV0158W, FPEV0159W, and FPEV0160I (January 2008)
  • Update 14: New messages FPEV0268E, FPEV0269E, FPEV0270E in PK44318 (January 2008)
  • Update 15: New messages FPEV2716W, FPEV2717W, FPEV2718E (January 2008)
  • Update 16: New messages FPEV0257I and FPEV1209I in PK53599 (January 2008)
  • Update 17: New message KO2I0215U in PK59371 (February 2008)
  • Update 18: New message FPEI0100S in PK62218 (February 2008)
  • Update 19: Correction to message KO2O0555I in PK48849 (April 2008)
  • Update 20: New message KO2I0212U in PK57152 (April 2008)
  • Update 21: New messages KO2O1366E and KO2O1367I in PK48849 (May 2008)
  • Update 22: New and revised messages KO2H13xx and KO2H14xx in PK59230 (May 2008)
  • Update 23: Revised message FPEV0198I in PK69740 (August 2008)
  • Update 24: New message KO2O1963I in PK27397 (September 2008)
  • Update 25: New messages FPET1030W and FPE1040W in PK75019 (November 2008)
  • Update 26: New and changes messages KO2I01xx in PK77333 (December 2008)
  • Update 27: Correction of messages FPEV0158W and FPEV0162W in PK76122 (January 2009)
  • Update 28: Correction of message FPEV0571I in PK76667 (January 2009)
  • Update 29: New message KO2O0952E in PK77656 (February 2009)
  • Update 30: Modified user response for message FPEV0560E in PK97285 (October 2009)
  • Update 31: Modifications to KO2O092xE messages in PK86834 (November 2009)
  • Update 32: New message KO2O1165W in PK87781 (December 2009)
  • Update 33: New message KO2O1294E in PK78190 (June 2010)
  • Update 34: New message FPEC4004E in PM24117 (March 2011)



------------------------------------------------------------------------
KO2O1963I Backlevel Near-Term History data set(s) detected. Resetting.

Explanation:

Near-term history VSAM data sets from a previous version of Near-Term
History Data Collector were found. These data sets are not compatible
with the current Near-Term History Data Collector.

System action:

The near-term history VSAM data sets are cleared and the Near-Term
History Data Collector will start.

User response:

None.

------------------------------------------------------------------------

Update 1: New Utility Services messages FPEU0011U and FPEU0015I in PK29544 (January 2007)

FPEU0011U UNABLE TO INIT BASE SERVICES

Explanation: An error occurred during initialization of the base services. This message should be accompanied by another message indicating the problem.

User response: Refer to the accompanying message to correct the error.

------------------------------------------------------------------------
FPEU0015I SECOND SESSION NOT SUPPORTED

Explanation: A second session of the OMEGAMON XE for DB2 PE ISPF Online Monitor is started in a ISPF split screen session. This second session is not supported.

User response: None

------------------------------------------------------------------------

Update 2: Message KO2O1915W provides more information in PK29492 (January 2007)
VTAM Display Logic Message KO2O1915W is revised as follows:

KO2O1915W - IFI COLLECTOR REACHED MAXIMUM STORAGE AMOUNT <V1> <V2> <V3> <V4> <V5> <V6> <V7>

Explanation: IFI collector did not read all of the data because the maximum buffer size was exceeded.
<V1> is the buffer size.
<V2> is the number of bytes moved to the buffer.
<V3> is the number of bytes not moved to the buffer.
<V4> is the global reason code.
<V5> is the return code.
<V6> is the reason code.
<V7> are the IFCIDs (two bytes per IFCID).

System action: Processing continues.

User response: Contact IBM support.

------------------------------------------------------------------------

Update 3: New messages FPEV0220W and FPEV0221W in PK27502 (February 2007)

FPEV0220W <V1> COMMAND FAILED. THE SPECIFIED DB2
SUBSYSTEM <V2> IS NOT RECOGNIZED BY THE DATA SERVER.

Explanation:
The subtask command issued to the Performance Expert Server subtask (PESERVER) failed
because the specified identifier of the DB2 subsystem is not recognized by the Performance Expert Server.
<V1> is the name of the master controller inside the OMEGAMON server (MSTR).
<V2> is the DB2 subsystem identifier.

User Response:
Verify that the specified DB2 subsystem exists and that the DB2 subsystem identifier is spelled correctly
in the command string. Correct and reissue the command.

------------------------------------------------------------------------
FPEV0221W <V1> COMMAND FAILED. THE DATA SERVER INSTANCE FOR
THE SPECIFIED DB2 SUBSYSTEM <V2> IS NOT RUNNING.

Explanation:
The subtask command issued to the Performance Expert Server subtask (PESERVER) failed
because the server instance for the specified DB2 subsystem is not running.

Possible reasons that the server instance failed include the following:
- the Performance Expert Server subtask was not started because the Performance Expert Server
is not configured to start monitoring for the specified DB2 subsystem.
- the Performance Expert Server subtask terminated because the DB2 subsystem terminated.
- the Performance Expert Server ended abnormally.

<V1> is the name of the master controller inside the OMEGAMON server (MSTR).
<V2> is the DB2 subsystem identifier.

User Response:
Verify that the Performance Expert Server subtask is configured to monitor the specified DB2 subsystem
and that the DB2 subsystem is running. Restart the Performance Expert Server subtask and reissue the command.

------------------------------------------------------------------------

Update 4: New messages KO2I0180U, KO2I0204U, and KO2I0212I in PK35988 (May 2007)

KO2I0180U LOCAL DAPICOMM STORAGE RELEASE ERROR

Explanation: The XE Agent failed to release a local storage communication structure used to communicate with the D5API common collector.

System action: Normal disconnect processing continues.

User response: Notify the IBM technical support center.

------------------------------------------------------------------------
KO2I0204U LOCAL DAPICOMM STORAGE OBTAIN ERROR

Explanation: The XE Agent failed to obtain local storage for the communication structure required to perform a connect call to the D5API common collector.

System action: The XE agent connect call is rejected.

User response: Increase the XE agent address space region size and restart the agent started task.

------------------------------------------------------------------------
KO2I0212I AGENT SUCCESSFULLY RELEASED DAPICOMM STRUCTURE FOR DB2 ssid

Explanation: The XE Agent successfully released the local storage communication structure used to communicate with the D5API common collector.

System action: Normal disconnect processing continues.

User response: None.

Update 5: Remark about OBnnnn messages from OMEGAMON base code (May 2007)

OB nnnn messages are from OMEGAMON base code that resulted from the merge of previous IBM DB2 PE and Candle products. These messages are made available in IBM Tivoli Monitoring z/OS Messages, which can be found at::

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc

Select "Monitoring," then "Reference Guides," then "z/OS Messages".

------------------------------------------------------------------------

Update 6: Update 6: New message KO2O1161E in PK44154 (May 2007)

KO2O1161E MULTIPLE PLAN NAMES AND MULTIPLE AUTHIDS MAY NOT BE SPECIFIED CONCURRENTLY

Explanation: DB2 Trace processing limits the -START TRACE command to either:
  • Up to five PLANNAMEs and one AUTHID
- or -
  • One PLANNAME and up to five AUTHIDs

System action: None

User response: Correct the trace options so that there are only multiple occurences of either the PLANNAME or the AUTHID.

------------------------------------------------------------------------

Update 7: Several new and changed messages (June 2007)

DGOP17 Performance Warehouse is not available.

Explanation:

Possible reasons are:
* The Performance Expert Server installation is still in progress or
incomplete.
* The database alias that you specified in the New Performance
Warehouse window does not reference a Performance Warehouse.
* The specified database alias refers to a performance database of a
Performance Expert version 3.1 or later.

User response:

1. Check the status of the Performance Expert Server installation.
2. If the installation completed successfully, use the Client
Configuration Assistant of DB2 to check the database alias that you
specified.
3. From version 3.1, you can no longer add a Performance Warehouse
system manually. Add the Performance Expert Server on which the
Performance Warehouse resides to your Performance Expert Client and
open Performance Warehouse from the System Overview window.

------------------------------------------------------------------------
FPEV0222I <V1> INSTANCE FOR DB2 SUBSYSTEM <V2> IS STARTED

Explanation:

The instance of the OMEGAMON Server subtask PESERVER, which is
monitoring this DB2 subsystem, is started.
* <V1> is the name of the master controller inside the OMEGAMON server
(MSTR) or the DB2 subsystem identifier.
* <V2> is the DB2 subsystem identifier.

User response:

None.

------------------------------------------------------------------------
FPEV0223I <V1> INSTANCE FOR DB2 SUBSYSTEM <V2> IS STOPPED

Explanation:

The instance of the OMEGAMON Server subtask PESERVER, which is
monitoring this DB2 subsystem, is stopped.
* <V1> is the name of the master controller inside the OMEGAMON server
(MSTR) or the DB2 subsystem identifier.
* <V2> is the DB2 subsystem identifier.

User response:

None.

-----------------------------------------------------------------------
FPEV3013E <V1> A TIMEOUT OCCURRED WHILE PROCESSING A REQUEST.

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.

------------------------------------------------------------------------
KO2O1161E MULTIPLE PLAN NAMES AND MULTIPLE AUTHIDS MAY NOT BE SPECIFIED
CONCURRENTLY

Explanation:

DB2 Trace processing limits the -START TRACE command to either:
* Up to five PLANNAMEs and one AUTHID
* One PLANNAME and up to five AUTHIDs

System action:

None

User response:

Correct the trace options so that there are only multiple occurrences of
either the PLANNAME or the AUTHID.

------------------------------------------------------------------------
KO2O1924I EPS1 <KO2PLAN> NOT USING IFI INTERFACE

Explanation:

The DB2 plan needed by OMPE has not been bound to this DB2. OMEGAMON
cannot use the IFI interface and cannot obtain complete monitoring
information.

System action:

Processing ends normally.

User response:

None.

------------------------------------------------------------------------
KO2R0134E VSAM OBJECT DEFINITION CHANGED. PLEASE RECREATE VSAM
DATASET(S). RC=12

Explanation:

The VSAM object definition has changed after installation of PTF
UK26200.

System action:

Processing continues.

User response:

Recreate H2 VSAM data sets by using the sample JCL described in the
README file accompanying the PTF.

------------------------------------------------------------------------
KO2R0135E CAPTURE OPEN OBJECT FAILURE - RC=retcode, msgText

Explanation:

An internal error occurred.

System action:

An SVC dump was generated.

User response:

Send the SVC dump with retcode and msgText to IBM support center.

------------------------------------------------------------------------

Update 8: New messages FPEV0266I and FPEV0267I (August 2007)

FPEV0266I <V1> EXCEPTION PROCESSING DIAGNOSTIC DATA: <V2>

Explanation:

One of the following occurred:
* The monitored DB2 subsystem did not return IFCID data within a
specified amount of time when periodic exception processing requested
the data.
* The timed out DB2 is the PWH that did not insert the found exceptions
within the specified amount of time.

* <V1> is the DB2 subsystem ID.
* <V2> specifies whether the timeout happened on the monitored DB2, or
on the PWH.

User response:

If this message only appears once, then it can be ignored. If it
appears many times for one DB2 subsystem, then contact your DB2
administrator.

------------------------------------------------------------------------
FPEV0267I <V1> EXCEPTION PROCESSING DIAGNOSTIC DATA: RA PRESERVED FOR
LATER USE

Explanation:

The return area (RA) will be reused for the next DB2 IFI request.
* <V1> is the DB2 subsystem ID.

User response:

None.

Update 9: New message KO2I0929E in PK50364 (August 2007)

KO2I0929E UNSUPPORTED IMS VERSION <V1>

Explanation:

An active thread originated from an IMS version that is not supported by
the product.
* <V1> is the unsupported IMS version.

System action:

IMS-specific information, such as transaction ID, is displayed as N/A.

User response:

Request a product upgrade for support of IMS version <V1>.

------------------------------------------------------------------------

Update 10: New messages KO2R136E to KO2R262E in PK44284 (August 2007)

KO2R136E Capture object open failure - Description mismatch. Redefine
file

Explanation:

Near-term history files were created by a previous maintenance level of
OMEGAMON. The VSAM files need to be deleted and redefined.

System action:

The Near-Term History Data Collector terminates.

User response:

Redefine the VSAM files.

------------------------------------------------------------------------
KO2R137E Capture object open failure - Server terminating

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R138E Capture server failure - Unable to create object - Object not
defined to container

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R139E Capture server failure - Unable to create object - Storage
unavailable

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R240E Capture server failure - Container is not initialized for
output

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R241E Capture object open failure - Data set not found

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Check the configuration.

------------------------------------------------------------------------
KO2R242E Capture server failure - Data set is not initialized for read

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R243E Capture server failure - Invalid area parameter

Explanation:

The Near-Term History Data Collector has detected an invalid parameter.

System action:

The Near-Term History Data Collector skips processing this request. A
dump is produced.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R244E Capture server failure - Invalid area length parameter

Explanation:

The Near-Term History Data Collector has detected an invalid length.

System action:

The Near-Term History Data Collector skips processing this request. A
dump is produced.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R245E Capture server failure - No user buffers

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R246E Capture server failure - Invalid access path not open for
input

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R247E Capture server failure - Invalid start or end times

Explanation:

The Near-Term History Data Collector has detected a record with an
invalid time.

System action:

The Near-Term History Data Collector skips processing this record. A
dump is produced.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R248E Capture server failure - I/O errors encountered on data

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R249E Capture server failure - Invalid argument list detected

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R250E Capture server failure - Cannot obtain retrieve buffer

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R251E Capture server failure - Invalid sequence return area

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R252E Capture server failure - Invalid data return area

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

-----------------------------------------------------------------------
KO2R253E Capture server failure - Invalid qualify subtype

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R254E Capture server failure - Invalid path type for request not
open for output

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R255E Capture server failure - User request abended

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R256E Capture server failure - Disconnect failed. Already
disconnected

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R257E Capture server failure - Primary path failed to close

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R258E Capture server failure - Unable to obtain argument list area

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R259E Capture server failure - Invalid maximum record parameter

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R260E Capture server failure - Invalid object return area

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R261E Capture server failure - Invalid version return area

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2R262E Capture server failure - Invalid request type

Explanation:

The Near-Term History Data Collector has terminated.

System action:

The Near-Term History Data Collector terminates.

User response:

Contact IBM support.

------------------------------------------------------------------------

Update 11: New messages KO2I0186U to KO2I0213U in PK50388 (October 2007)

KO2I0186U DB2 %%%% CONNECTION ALREADY EXISTS IN OM %%%%%%%% - CONNECT
CALL REJECTED

Explanation:

The D5API Connect call failed because a DB2 connection already exists.

System action:

The Connect call is rejected.

User response:

Shut down and restart the Agent address space.

------------------------------------------------------------------------
KO2I0203U DAPICOMM STRUCTURE CELL ELEMENT OBTAIN FAILURE

Explanation:

The D5API call failed to obtain a communication data structure that is
required to communicate Connect calls to the common collector.

System action:

The Connect call is rejected.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2I0205U UNABLE TO LOCATE COMMON COLLECTOR REGISTRY ENTRY FOR OM
SERVER %%%%%%%%

Explanation:

The D5API call could not locate the common collector registry for the
specified OMEGAMON server.

System action:

The Connect, Collect, or Disconnect call is terminated.

User response:

Verify that the OMEGAMON server that the Agent is trying to communicate
with is active in the system. If it is not active, start the OMEGAMON
server.

------------------------------------------------------------------------
KO2I0206U UNABLE TO VALIDITY-CHECK DAPICOMM STRUCTURE STATUS DUE TO
QUEUE SCAN FAILURE

Explanation:

The D5API call failed to locate the communication data structure that is
required to process the common collector Collect or Disconnect call.

System action:

The Collect or Disconnect call is rejected.

User response:

Contact IBM support.

------------------------------------------------------------------------
KO2I0213U UNABLE TO LOCATE SPECIFIED DB2=%%%% SUBSYSTEM - %%%%%%%%
CALL FAILED

Explanation:

The D5API Connect or Collect call failed because the DB2 subsystem was
not found.

System action:

The Connect or Collect call is rejected.

User response:

Start the specified DB2 subsystem.


Update 12: New message KO2R1155I in PK56009 (January 2008)

KO2R1155I DSN USED FOR CAPTURE : dsname

Explanation:

A user has captured an application trace to data set dsname.

System action:

The trace is completed.

User response:

None.

------------------------------------------------------------------------

Update 13: Correc tion of messages FPEV0158W, FPEV0159W, and FPEV0160I (January 2008)

FPEV0158W <V1> <V2> DATA SERVER DETECTED HIGH CPU USAGE (<F3> %) OF
TASK <V4>.

Explanation:

Performance Expert detects high CPU usage for one of its components.
* <V1> is the DB2 subsystem ID.
* <V2> is the local time.
* <F3> is the detected CPU usage.
* <V4> is the name of the task.

The OMEGAMON Server subtask PESERVER periodically monitors the CPU
consumption of its subtasks in intervals of one minute. If the CPU
consumption of a subtask exceeds the internal threshold value of 40%,
the server issues message FPEV0158W. Additionally, the internal server
traces are started and message FPEV0162W is issued. If the CPU
consumption of the subtask falls below the threshold within the next
sample interval, the internal traces are switched off and normal
processing continues. If the CPU consumption of the subtask remains
above the threshold within the next sample interval, a dump is taken and
message FPEV0159W is issued. If the CPU consumption of the subtask
continues to exceed the threshold, the subtask will finally be
reattached and message FPEV0161W is issued.

User response:

None.

------------------------------------------------------------------------
FPEV0159W <V1> <V2> DUMP IS WRITTEN FOR FURTHER ANALYSIS OF HIGH CPU
USAGE

Explanation:

Performance Expert detects high CPU usage for one of its components and
starts to dump data for further analysis. The dump is taken for the
second occurrence of high CPU usage. The message is preceded by message
FPEV0158W.
* <V1> is the DB2 subsystem ID.
* <V2> is the local time.

User response:

Save the dump for further analysis by IBM.

------------------------------------------------------------------------
FPEV0160I <V1> <V2> GPR <F3>-<F4>: '<V5>'X, '<V6>'X, '<V7>'X, '<V8>'X

Explanation:

Performance Expert detects high CPU usage for one of its components and
starts to write the contents of the general purpose registers to the log
for further analysis. The message is issued for the second occurrence of
high CPU usage. The message is preceded by message FPEV0159W.
* <V1> is the DB2 subsystem ID.
* <V2> is the local time.
* <F3> to <F4> is the range of registers.
* <V5> to <V8> are the register contents.

User response:

Save the Performance Expert log (SYSPRINT) for further analysis by IBM.

------------------------------------------------------------------------

Update 14: New messages FPEV0268E, FPEV0269E, FPEV0270E in PK44318 (January 2008)

FPEV0268E <V1> PERIODIC EXCEPTION LOG DATA SET <V2> HAS WRONG SETTINGS.
SETTINGS FOUND: RECFM = <V3>, LRECL = <V4>

Explanation:

The Periodic Exception Log data set was allocated incorrectly.
* <V1> is the DB2 subsystem ID.
* <V2> is the data set name.
* <V3> is the record format.
* <V4> is the record length.

User response:

Reallocate the Periodic Exception Log data set using the correct attributes.

RECFM VB
LRECL >=512

------------------------------------------------------------------------
FPEV0269E <V1> PERIODIC EXCEPTION FILE DATA SET <V2> HAS WRONG
SETTINGS. SETTINGS FOUND: RECFM = <V3>, LRECL = <V4>

Explanation:

The Periodic Exception File data set was allocated incorrectly.
* <V1> is the DB2 subsystem ID.
* <V2> is the data set name.
* <V3> is the record format.
* <V4> is the record length.

User response:

Reallocate the Periodic Exception File data set using the correct attributes.

RECFM VBS
LRECL >=32756

------------------------------------------------------------------------
FPEV0270E <V1> PERIODIC EXCEPTION THRESHOLD DATA SET <V2> HAS WRONG
SETTINGS. SETTINGS FOUND: RECFM = <V3>, LRECL = <V4>. PERIODIC
EXCEPTION PROCESSING NOT STARTED.

Explanation:

The Periodic Exception Threshold data set was allocated incorrectly.
* <V1> is the DB2 subsystem ID.
* <V2> is the data set name.
* <V3> is the record format.
* <V4> is the record length.

User response:

Reallocate the Periodic Exception File data set using the correct attributes.

RECFM VB
LRECL >=255

------------------------------------------------------------------------

Update 15: New messages FPEV2716W, FPEV2717W, FPEV2718E (January 2008)

FPEV2716W <V1> DB2 MESSAGES SUPPORT TASK NOT STARTED. THE COMMAND IS
IGNORED

Explanation:

This message is issued in response to a MODIFY command. You tried to stop the DB2 Messages support task, but this task is already stopped.
* <V1> is the DB2 subsystem ID.

User response:

None.

------------------------------------------------------------------------
FPEV2717W <V1> DB2 MESSAGES SUPPORT TASK IS ACTIVE. THE COMMAND IS
IGNORED

Explanation:

This message is issued in response to a MODIFY command. You tried to start the DB2 Messages support task while this task is already active.
* <V1> is the DB2 subsystem ID.

User response:

None.

------------------------------------------------------------------------
FPEV2718E <V1> DB2 MESSAGES SUPPORT TASK IS NOT SUPPORTED FOR THIS DB2
VERSION

Explanation:

This message is issued in response to a MODIFY command. You tried to start or stop the DB2 Messages support task for a DB2 subsystem version that is not supported. The DB2 Messages support task is only supported for DB2 Version 8 and later.
* <V1> is the DB2 subsystem ID.

User response:

None.

------------------------------------------------------------------------

Update 16: New messages FPEV0257I and FPEV1209I in PK53599 (January 2008)

FPEV0257I <V1> CAF ERROR WHEN EXCEPTION EVENT ATTEMPTED TO DISCONNECT
FROM DB2. RC <V2>, REASON <V3>

Explanation:

This message is self-explanatory.
* <V1> is the DB2 subsystem ID.
* <V2> is the IFI return code.
* <V3> is the IFI reason code.

User response:

Refer to DB2 Messages and Codes (or the corresponding manual of the DB2
version you have installed) for an explanation of the return and reason
codes.


------------------------------------------------------------------------
FPEV1209I <V1> APPLICATION SERVICES - CAF ERROR WHEN ATTEMPTED TO
DISCONNECT FROM DB2. RC <V2>, REASON <V3>

Explanation:

This message is self-explanatory.
* <V1> is the DB2 subsystem ID.
* <V2> is the Call Attach Facility (CAF) return code.
* <V3> is the CAF reason code.

User response:

Refer to DB2 Messages and Codes (or the corresponding manual of the DB2
version you have installed) for an explanation of the return and reason
codes.

------------------------------------------------------------------------

Update 17: New message KO2I0215U in PK59371 (February 2008)

KO2I0215U IFI SUBTASK IS INACTIVE FOR AGENT <V1>, TABLE=<V2>,
DB2=<ssid>

Explanation:

This message is self-explanatory.

System action:

None.

User response:

None.

------------------------------------------------------------------------

Update 18: New message FPEI0100S in PK62218 (February 2008)

FPEI0100S THE SPECIFIED ORDERING SEQUENCE IS NOT SUPPORTED.

Explanation:

If the ordering sequence contains PARTNBR together with other criteria
the buffer pool report will only be ordered and created if PARTNBR is
preceded by PAGESET.

User response:

If PARTNBR is your favourite criteria then specify an order sequence
that contains PAGESET before PARTNBR. Then rerun the job.

------------------------------------------------------------------------

Update 19: Correction to message KO2O0555I in PK48849 (April 2008)

KO2O0555I NEAR-TERM HISTORY DATA COLLECTOR - A BATCH JOB IS SUBMITTED
TO FLUSH THE CONTENTS OF THE H2 DATA SET

Explanation:

This is an informational message.

System action:

Processing continues.

User response:

None.

------------------------------------------------------------------------

Update 20: New message KO2I0212U in PK57152 (April 2008)

KO2I0212U UNABLE TO LOCATE A CONNECTION TO DB2=ssid IN OM SERVER
server-name - [COLLECT | DISCONNECT] CALL FAILED

Explanation:

The D5API call was unable to locate a connection for the specified DB2
subsystem on the target OMEGAMON server.

System action:

The specified D5API call is terminated and error and reason codes are
returned to the calling agent.

User response:

Contact IBM support.

------------------------------------------------------------------------

Update 21: New messages KO2O1366E and KO2O1367I in PK48849 (May 2008)

KO2O1366E SEQ OUTPUT NEEDS DISP=OLD,DSN=xxx

Explanation:

An attempt to allocate a new sequential file xxx or GDG generation
xxx(+1) failed. Another process has an existing allocation against the
file or GDG base xxx.

System action:

This message is issued once. The Near-Term History Data Collector
retries the allocation once a second. When the other process releases
its allocation, the sequential file is allocated, output is resumed, and
confirmation message Message KO2O1367I is issued.

User response:

None. If required, the holding owner of the sequential file or GDG base
can be determined by issuing the operator command D
GRS,RES=(SYSDSN,xxx), where xxxis the DSN= value from the message.

------------------------------------------------------------------------
KO2O1367I SEQ OUTPUT NOW RESUMED DSN=xxx

Explanation:

A previously locked data set has successfully been allocated.

System action:

The Near-Term History Data Collector continues writing IFCID trace
output to the new sequential file.

User response:

None.

------------------------------------------------------------------------

Update 22: New and revised messages KO2H13xx and KO2H14xx in PK59230 (May 2008)

KO2H1376I NEAR-TERM HISTORY DATA COLLECTOR - ONLY ONE DATASET NAME
ALLOWED WITH @DATE@TIME OR GDG(+1)

Explanation:

More than one specification of a data set was found in parameter
SEQDATASET in RKD2PAR(COPTcccc). If the variables @DATE and @TIME are
used in the specification of a data set name, or if a Generation Data
Group (GDG) name is specified, only a single data set name is allowed.

System action:

Processing continues.

User response:

Check and correct the SEQDATASET parameter value.


------------------------------------------------------------------------
KO2H1378I NEAR-TERM HISTORY DATA COLLECTOR - GDG SPEC IS NOT COMPATIBLE
WITH @DATE@TIME VARIABLES

Explanation:

The use of variables @DATE and @TIME is not allowed in the specification
of a Generation Data Group (GDG) data set name.

System action:

Processing continues.

User response:

Correct the data set name in the SEQDATASET parameter in
RKD2PAR(COPTcccc).


------------------------------------------------------------------------
KO2H1379I NEAR-TERM HISTORY DATA COLLECTOR - @DATE REQUIRES @TIME TO
ASSURE UNIQUE DATA SET NAMES

Explanation:

Either variable @DATE or @TIME was found in the specification of a data
set name in parameter SEQDATASET in RKD2PAR(COPTcccc). However, to
ensure a unique data set name, both variables must be used in the
specification.

System action:

Processing continues.

User response:

Check and correct the SEQDATASET parameter value.


------------------------------------------------------------------------
KO2H1384I NEAR-TERM HISTORY DATA COLLECTOR - ALLOCATION SPACE AMOUNT
INVALID

Explanation:

The SPACE parameter in RKD2PAR(COPTcccc) contains a wrong value for the
primary or secondary allocation, or both.

System action:

Processing continues.

User response:

Check and correct the SPACE parameter value.


------------------------------------------------------------------------
KO2H1400I NEAR-TERM HISTORY DATA COLLECTOR - THE MESSAGE NUMBER
message-id IS NOT DEFINED

Explanation:

The system attempted to write a message while parsing RKD2PAR(COPTcccc),
but could not find the indicated message-id.

System action:

Processing continues.

User response:

Contact IBM support.


------------------------------------------------------------------------
KO2H1403E NEAR-TERM HISTORY DATA COLLECTOR - WRITEOPTION KEYWORD VALUE VSAM
MISSING

Explanation:

The indicated keyword value is missing.

System action:

Processing terminates.

User response:

Check the indicated keyword values and make the necessary changes.
Resubmit the request.


------------------------------------------------------------------------
KO2H1405W NEAR-TERM HISTORY DATA COLLECTOR - KEYWORDS
DYNAMICSQL/LOCKCONT/LOCKSUSP IGNORED. (WRITEOPTION WITHOUT VSAM)

Explanation:

The keywords DYNAMICSQL, LOCKCONT, and LOCKSUSP are only valid with
WRITEOPTION(VSAM) or WRITEOPTION(VSAM,SEQ).

System action:

The Near-Term History Data Collector terminates.

User response:

None.

------------------------------------------------------------------------

Update 23: Revised message FPEV0198I in PK69740 (August 2008)

FPEV0198I <V1> AUTODETECT=<V2>

Explanation:

This message is issued in response to a DISPLAY command or during
OMEGAMON Server startup. If auto-detection of DB2 subsystems by the
OMEGAMON Server PESERVER subtask is switched off, <V2> is NO, otherwise
YES.
* <V1> is the DB2 subsystem ID.
* <V2> is either YES or NO.

User response:

None.

------------------------------------------------------------------------

Update 24: New message KO2O1963I in PK27397 (September 2008)

KO2O1963I Backlevel Near-Term History data set(s) detected. Resetting.

Explanation:

Near-term history VSAM data sets from a previous version of Near-Term
History Data Collector were found. These data sets are not compatible
with the current Near-Term History Data Collector.

System action:

The near-term history VSAM data sets are cleared and the Near-Term
History Data Collector will start.

User response:

None.

------------------------------------------------------------------------

Update 25: New messages FPET1030W and FPE1040W in PK75019 (November 2008)

FPET1030W THE INTERNAL LIMIT OF PHASES THAT CAN BE PROCESSED HAS BEEN
EXCEEDED. PROCESSING CONTINUES WITH V1 REGISTERED PHASES WITHOUT
ADDITIONAL ONES.

Explanation:

Processing is limited to V1 phases. New phases found after reaching this
limit cannot be processed.

User response:

Ensure that the input trace data does not include more than the maximum
number of phases.

------------------------------------------------------------------------
FPET1040W THE INTERNAL LIMIT OF SUBTASKS THAT CAN BE PROCESSED HAS BEEN
EXCEEDED. PROCESSING CONTINUES WITH V1 REGISTERED SUBTASKS WITHOUT
ADDITIONAL ONES.

Explanation:

Processing is limited to V1 subtasks. New phases found after reaching
this limit cannot be processed.

User response:

Ensure that the input trace data does not include more than the maximum
number of subtasks. For example, check and adapt the PARALLEL option of
the COPY or RECOVER utility when collecting DB2 trace data.

------------------------------------------------------------------------

Update 26: New and changes messages KO2I01xx in PK77333 (December 2008)


KO2I0189I AGENT %%%%%%%% ATTEMPTING CONNECTION TO %%%%%%%% VERSION V410
BY %%%%%%%% - DB2 %%%%

Explanation:

An OMEGAMON XE for DB2 PE agent is attempting a connection to the
indicated OMEGAMON common collector for the indicated DB2 system.

System action:

The agent is attempting a connection.

User response:

None.

------------------------------------------------------------------------
KO2I0190W CONNECT TIME LIMIT EXCEEDED. CONNECT CALL FAILED

Explanation:

The OMEGAMON XE D5API Collector Agent connection function exceeded the
internally specified nine minutes connect time allowance.

System action:

The Agent Connect call is terminated.

User response:

Check the OMEGAMON collector job log or OMEGAMON XE for DB2 PE agent
RKLVLOG for possible causes.

------------------------------------------------------------------------
KO2I0193I AGENT %%%%%%%% CONNECTED TO %%%%%%%% - DB2 %%%%

Explanation:

The OMEGAMON XE for DB2 PE agent successfully connected to the OMEGAMON
common collector for the indicated DB2 subsystem.

System action:

The agent Connect call succeeded.

User response:

None.

------------------------------------------------------------------------
KO2I0194I AGENT %%%%%%%% FAILED TO CONNECT TO %%%%%%%% - DB2 %%%%

Explanation:

The OMEGAMON XE for DB2 PE agent failed to connect to the OMEGAMON
common collector for the indicated DB2 subsystem.

System action:

The agent Connect call failed.

User response:

Check the OMEGAMON collector job log or OMEGAMON XE for DB2 PE agent
RKLVLOG for possible causes.

------------------------------------------------------------------------
KO2I0195I AGENT %%%%%%%% DISCONNECTED FROM %%%%%%%% - DB2 %%%%

Explanation:

The OMEGAMON XE for DB2 PE agent disconnected from the OMEGAMON common
collector for the indicated DB2 subsystem.

System action:

The agent is disconnected from the common collector.

User response:

None. It might be that the OMEGAMON common collector or DB2 system was
recycled.


Update 27: Correction of messages FPEV0158W and FPEV0162W in PK76122 (January 2009)

FPEV0158W <V1> <V2> DATA SERVER DETECTED HIGH CYCLE TASK USAGE (<F3> %)
IN TASK <V4>.

Explanation:

Performance Expert detects high cycle task usage for one of its
components.
* <V1> is the DB2 subsystem ID.
* <V2> is the local time.
* <F3> is the detected cycle usage.
* <V4> is the name of the task.

The OMEGAMON Collector subtask PESERVER periodically monitors the CPU cycle
consumption of its subtasks in intervals of one minute. If the CPU cycle
consumption of a subtask exceeds an internal threshold value, the server
issues message FPEV0158W. The threshold value may vary with situation
and subtask. Cycle usage is not percentage usage of total system CPU,
but is the percentage usage of the maximum CPU available to that task -
typically percentage usage of a single CPU. Additionally, the internal
server traces are started and message FPEV0162W is issued. If the cycle
consumption of the subtask falls below the threshold within the next
sample interval, the internal traces are switched off and normal
processing continues. If the CPU consumption of the subtask remains
above the threshold within the next sample interval, a dump is taken and
message FPEV0159W is issued. If the cycle consumption of the subtask
continues to exceed the threshold, the subtask will finally be
reattached and message FPEV0161W is issued.

User response:

This occurs singly on rare occasions because of brief spikes in resource
usage and can be ignored. If this occurs regularly and there is no
obvious cause, then the server trace can be sent to IBM support for
investigation.


------------------------------------------------------------------------
FPEV0162W <V1> <V2> TRACES ARE STARTED FOR FURTHER ANALYSIS OF HIGH
SUBTASK USAGE.

Explanation:

Performance Expert detects high cycle usage for one of its components
and is starting internal traces for further analysis. The message is
preceded by message FPEV0158W.
* <V1> is the DB2 subsystem ID.
* <V2> is the local time.
* <V3> is the name of the task.

User response:

If this situation occurs regularly with no obvious cause then save the
Performance Expert log (SYSPRINT) for further analysis by IBM.



Update 28: Correction of message FPEV0571I in PK76667 (January 2009)

FPEV0571I <V1> OLD HISTORY DATA SET <V2> SUCCESSFULLY ARCHIVED

Explanation:

The old history data set was successfully archived and a new one was
created.
* <V1> is the DB2 subsystem ID.
* <V2> is the name of the archived data set.

User response:

If you are asked by IBM support to keep the archived data set for
further problem analysis, use the REPRO command of the IDCAMS utility to
save the data set.

------------------------------------------------------------------------

Update 29: New message KO2O0952E in PK77656 (February 2009)

KO2O0952E GETMEM > LIMIT: X1 T1 R1 W1 C1 R14=X2

Explanation:

An internal memory request was denied. If allowed, the address space
will run short on storage.
* X1 is the requested amount.
* T1 is the request type.
* R1 is the requesting routine name.
* W1 is the requested work area.
* C1 is the calling routine.
* X2 is the requesting return address.

System action:

The memory request is denied.

User response:

Contact IBM support.

------------------------------------------------------------------------

Update 30: Modified user response for message FPEV0560E in PK97285 (October 2009)

FPEV0560E <V1> DB2 RETURNED INCORRECT DATA. REQUEST CANCELED

Explanation:

Incorrect READS data was found, so the request to retrieve data was
canceled.
* <V1> is the DB2 subsystem ID.

User response:

If the error recurs, trace the problem using the Data Server trace
(tracelevel=36) and contact IBM support. Keep the archived SVC dump
titled INCORRECT RA - DB2I and all JES outputs of OMEGAMON Collector
Started Task for further analysis by IBM support.

------------------------------------------------------------------------


Update 31: Modifications to KO2O092xE messages in PK86834 (November 2009)

KO2O0920E FAILED TO LOCATE DB2 CONTROL BLOCK cccc FOR xxxx. TERMINATING

Explanation:

OMEGAMON XE for DB2 PE could not locate the indicated main DB2 cccc
control block during initialization.

System action:

Processing terminates.

User response:

Verify that the specified DB2 xxxx is active, and restart OMEGAMON XE
for DB2 PE.

------------------------------------------------------------------------
KO2O0921E FAILED TO LOCATE IRLM CONTROL BLOCK ccccc FOR xxxx.
TERMINATING

Explanation:

OMEGAMON XE for DB2 PE could not locate the indicated main Internal
Resource Lock Manager (IRLM) cccc control block during initialization.

System action:

Processing terminates.

User response:

Verify that the IRLM associated with DB2 xxxx is active, and restart
OMEGAMON XE for DB2 PE.

------------------------------------------------------------------------
KO2O0922E DB2 DBAS ADDRESS SPACE NOT YET ACTIVE FOR xxxx. TERMINATING

Explanation:

OMEGAMON XE for DB2 PE could not locate the database address space
(DBAS) for DB2 xxxx during OMEGAMON XE for DB2 PE initialization.

System action:

Processing terminates.

User response:

Verify that the DBAS address space initialized successfully. If not,
restart DB2 and then restart OMEGAMON XE for DB2 PE.

------------------------------------------------------------------------
KO2O0924E OMEGAMON XE FOR DB2 PE INITIALIZATION FAILED BECAUSE DB2 xxxx
IS TERMINATING

Explanation:

DB2 xxxx terminated during OMEGAMON XE for DB2 PE initialization.

System action:

Processing terminates.

User response:

Determine why DB2 terminated. Restart DB2 and then restart OMEGAMON XE
for DB2 PE.

------------------------------------------------------------------------
KO2O0925E OMEGAMON XE FOR DB2 PE INITIALIZATION TERMINATED BECAUSE DB2
xxxx IS NOT USABE

Explanation:

DB2 xxxx not usable during OMEGAMON XE for DB2 PE initialization.

System action:

Processing terminates.

User response:

Determine why DB2 not usable and then restart OMEGAMON XE for DB2 PE..

------------------------------------------------------------------------


Update 32: New message KO2O1165W in PK87781 (December 2009)

KO2O1165W APPLICATION TRACE DBID/OBID BUFFER FULL

Explanation:

The Application Trace Facility (ATF) buffer, used to hold DBID/OBID
information, is full. Some DBID/OBID will not be translated.

System action:

Processing continues.

User response:

Contact IBM support.

------------------------------------------------------------------------

Update 33: New message KO2O1294E in PK78190 (June 2010)

KO2O1294E UNABLE TO USE THREAD EXCEPTION PROFILE VARIABLE %%%%. MAY BE
FROM V520. DELETE/REDEFINE.

Explanation:

The thread exception profile contains unusable constructs, most likely
because the profile was carried over from V520.

User response:

Do not use the constructs in exception processing nor display them in
the profile. Let the user know when he or she logs off. Delete and
redefine the profile. It may be the installation profile, O2INSTAL, or
the user's profile.

------------------------------------------------------------------------

Related information

Messages Version 4.1.0

Publication number

SC18-9980-00

Original publication date

2007/11/28

Product Alias/Synonym

DB2PM

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:

4.1.0

Operating system(s):

z/OS

Reference #:

7008854

Modified date:

2011-03-23

Translate my page

Machine Translation

Content navigation