V 5.1.0: Updates of the manual "Messages" of the following products "IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS" and "IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS"

Manual


Abstract

This document covers updates of the manual "Messages" of the products IBM ® Tivoli® OMEGAMON for DB2® Performance Expert and Performance Monitor on z/OS, GH12-6923-00, for Version 5.1.0.

Content

Update 1: New message FPEC4004E in PM24117 (March 2011)

  • Update 2: New message KO2E3991E in PK90683 (March 2011)
  • Update 3: Changed message ID from KO2O1963I to KO2O1964I and new message KO2O1963E in PM33760 (March 2011)
  • Update 4: New FPEV21xx messages in PM27781 (April 2011)
  • Update 5: New KO2Ixxxxx messages in PM33760 (April 2011)
  • Update 6: New KO2xxxxxx messages (May 2011)
  • Update 7: New message KO2O0602W in PM36528 (May 2011)
  • Update 8: New message KO2Z069I (July 2011)
  • Update 9: New message FPEM0804I in PM44548 (August 2011) and updated messages FPEM0811I and FPEM0819I
  • Update 10: New messages FPEA0803I and FPEA0804I (August 2011)
  • Update 11: New messages KO2Z038E, KO2Z643W, KO2Z665W in PM44106 (August 2011)
  • Update 12: New message FPEM0806W in PM 46171 (November 2011)
  • Update 13: New messages FPEV2104I and FPEV2105I in PM52466 (December 2011)
  • Update 14: New message KO2R0112I in PM52470 and PM52468 (December 2011)
  • Update 15: New messages KO2Z659I and KO2Z662I in PM49637 (February 2012)
  • Update 16: New message KO2Z667I in PM55403 (April 2012)
  • Update 17: New message FPEM0807I in PM55120 (April 2012)
  • Update 18: New message KO2H0605I in PM62281 (May 2012)
  • Update 19: New message KO2Z091E in PM68972 (September 2012)
  • Update 20: Added message FPEV1342I (November 2012)
  • Update 21: New messages related to the Spreadsheet Input Data Generator (Dezember 2012)
  • Update 22: Changed message KO2Z665W in PM74343. (January 2013)
  • Update 23: PM85113 provides new Background Control messages that are related to long names with variable length. (May 2013)
  • Update 24: New message KO2O1369I in PI05484 (February 2014)
  • Update 25: New message FPEM229 (July 2014)

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

Update 25: New message FPEM229 (July 2014)

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 1: New message FPEC4004E in PM24117 (March 2011)


FPEC4004E INVALID RDW FOUND IN RECORD <F1>. PROCESSING TERMINATED

Explanation:

The record processing terminated because invalid input record with RDW=0 was encountered.

  • <F1> is the number of the invalid input record.

User response:

Try to copy input data set with invalid RDW encountered to another data set. It should fix the problem.

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

Update 2: New message KO2E3991E in PK90683 (March 2011)


KO2E3991E EVENTMGR INVALID START PARM SUPPLIED

Explanation:

This message is issued by the Event Manager to indicate that an invalid START parameter
has been specified in member EMGR<lpar> of the RKD2PAR parameter library.

System action:

Event Manager initialization is terminated.

User response:

Correct the parameter problem and restart the Event Manager.

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

Update 3: Changed message ID from KO2O1963I to KO2O1964I and new message KO2O1963E in PM33760 (March 2011)

KO2O1964I 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.


KO2O1963E OMEGAMON Server subtask PESERVER not active.

Explanation:

PESERVER subtask is not active. It may have been stopped with the command
/F <STC_Name>, P PESERVER
or during initialization, the START PESERVER command was not executed or failed.

System action:

Monitoring is not available.

User response:

Start the PESERVER subtask using the command
/F <STC_Name>, S PESERVER
Ensure that message FPEV0000I appears during initialization.

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

Update 4: New FPEV21xx messages in PM27781 (April 2011)


KO2E3991E EVENTMGR INVALID START PARM SUPPLIED

Explanation:

This message is issued by the Event Manager to indicate that an invalid START parameter
has been specified in member EMGR<lpar> of the RKD2PAR parameter library.

System action:

Event Manager initialization is terminated.

User response:

Correct the parameter problem and restart the Event Manager.



FPEV2100I <V1> <V2> ELAPSED PROCESSING TIME <V3> SEC FOR DB2 INTERFACE
TASK EXCEEDS THRESHOLD <V4> SEC

Explanation:

The time required by the DB2 interface task of the PE Server subtask to
complete a request exceeds the user-specified threshold value.
* <V1> is the DB2 subsystem ID.
* <V2> is the current time stamp.
* <V3> is the actual elapsed processing time.
* <V4> is the threshold value for the elapsed processing time.

User response:

The current time stamp and the actual elapsed processing time can be
used to further analyze the slowdown.



FPEV2101I <V1> DUMP INITIATED FOR OMEGAMON COLLECTOR AND DB2 ADDRESS
SPACES (<V2>)

Explanation:

This message is preceded by message FPEV2100I or FPEV2103I.
An SVC dump is initiated for the OMEGAMON Collector and the
DB2 address spaces of the DB2 subsystem that is currently handling
a call to the DB2 instrumentation facility interface issued by the
PE Server subtask.
* <V1> is the DB2 subsystem ID.
* <V2> is the list of address space IDs.

The address space identifiers are listed in the sequence OMEGAMON
Collector, DB2 MSTR, DB2 IRLM, DB2 DBM1, and DB2 DIST.

User response:

Provide the OMEGAMON Collector started task job output and dump to IBM
for further analysis.



FPEV2102W <V1> DB2 IFI RESPONSE TIME EXCEEDS MAX WAIT TIME BY <V2> SEC

Explanation:

A request issued to the DB2 instrumentation facility interface completed after expiration
of the maximum wait time of the calling DB2 interface task of the PE Server.
This message can indicate a slowdown in DB2.

* <V1> is the DB2 subsystem ID.
* <V2> is the time by which the maximum wait time is exceeded. A value of zero is displayed
if the maximum wait time is exceeded by less than one second.

User response:

Analyse the reason for the bad response time. A possible reason could be a
coincidence of other high priority tasks in DB2 or MVS.
More detailed diagnostics data can be achieved by setting a threshold value
for the elapsed processing time (EPTT) in the DB2 interface task of the PE Server.
The corresponding modify command EPTT is described in the
Configuration and Customization manual.



FPEV2103I <V1> <V2> ELAPSED PROCESSING TIME THRESHOLD EXCEEDED

Explanation:

The time required by the DB2 interface task of the PE Server subtask to
complete a request exceeds the user-specified threshold value.
* <V1> is the DB2 subsystem ID.
* <V2> is the current time stamp.

User response:

The current time stamp can be used to further analyze the slowdown.

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

Update 5: New KO2Ixxxxx messages in PM33760 (April 2011)

KO2I0553E OINT Jobstep Program: pppppppp. OMPE Subsystem required.

Explanation:

Program name 'pppppppp' is the name specified on the EXEC statement of the STC JCL. OMEGAMON XE for DB2 PE releases version 4.2.0 and higher require that PGM=KO2ZTOBP is specified on the EXEC statement of the STC JCL statement.

System action:

Started task terminates.

User response:

Specify PGM=KO2ZTOPB on the EXEC statement of the STC JCL statement.



KO2I0554E HINT Jobstep Program: pppppppp. OMPE Subsystem required.

Explanation:

Program name 'pppppppp' is the name specified on the EXEC statement of the STC JCL. OMEGAMON XE for DB2 PE releases version 4.2.0 and higher require that PGM=KO2ZTOBP is specified on the EXEC statement of the STC JCL statement.

System action:

Started task terminates.

User response:

Specify PGM=KO2ZTOPB on the EXEC statement of the STC JCL statement.

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


Update 6: New KO2xxxxxx messages (May 2011)



KO2O1368E NEAR-TERM HISTORY DATA COLLECTOR - INVALID RECORD RECEIVED

Explanation:

An IFI record with a length longer than expected or zero has been received.

System action:

The record is skipped and processing continues with the next record.

User response:

None.



KO2R0247W Capture Server Failure - Invalid start or end times

Explanation:

A near-term history record that was being written did not pass the date validity checks. The thread start or end date was zero, or the end data was greater than the start date.

System action:

The record is skipped and not written to the near-term history data set and processing continues with the next record.

User response:

None.

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

Update 7: New message KO2O0602W in PM36528 (May 2011)

Message (KO2O0602W %%%% Trace data lost - too many buffers in use.)

Explanation:

%%%% is the name of the affected DB2 subsystem. DB2 produces IFCID records faster than the
Near-Term History Collector can process. Currently, more than 15 buffers are used. The collection of IFCID records is suspended until 15 or less buffers are used.

System Action:

Records are skipped until the Near-Term History Collector can reduce the backlog of records to be processed.

User Response:

You can solve the problem by doing one or more of the following actions.

NOTE:
Use the Configuration Tool, previously called ICAT, panel KD261P8 and KD261PB, to modify the BUFSIZE-, NEGSQL-, SCAN-, SORT-, DYNAMICSQL- and POSTPCT- parameters below. If you do not use the Configuration Tool to record and update the parameter library, changes might be reversed the next time you are using it.

  • Increase the buffer size by setting its value to 2048. Try different values and evaluate the results.

    By default, the buffer size (BUFSIZE) is 1024. This value might be too small for high volume production systems. The upper limit for the buffer size is the maximum value for a -START TRACE command. For more information, see the DB2 commands reference.

    For the OMEGAMON Near-Term History collector, the recommended value for the buffer size is 2048.
  • Reduce the number of IFCIDs to be written to the OPx by using the following settings:
      • NEGSQL(NO)
        Use this setting to not collect return codes on SQL events:
        Affected IFCIDs: 58, 59, 60, 61, 62, 64, 65, 66, 233.

        If Near-Term History data is not collected to sequential files, there is no reason to collect this data. Near-Term History data is not externalized by the real time product. However, it can be externalized by batch reporting if it is collected to sequential files.
      • SCAN(NO)
        Use this setting to not collect SCAN data:
        Affected IFCIDs: 15, 16, 17, 18.
      • SORT(NO)
        Use this setting to not collect SORT data:
        Affected IFCIDs 95, 96.
      • DYNAMICSQL(NO)
        Use this setting to not collect SQL text from dynamic SQL statements:
        Affected IFCIDs: 22, 63.

        The collection of NEGSQL-, SCAN-, SORT-, and DYNAMICSQL-data results in a high volume of trace data that is generated by the DB2 subsystem.This increases the CPU utilization. Furthermore, it exposes the application to DSNW133I messages.
  • Reduce the POSTPCT value to read buffers more frequently. Try different values and evaluate the results.
    By default, the POSTPCT value is set to POSTPCT(70). This means that the OP buffers are read when they are full up to 70%.
  • Ensure that the OMPE collector task is running at the same or at a higher service level than the monitored DB2 subsystems.
  • Restart the OMEGAMON for DB2 started task to start using the modified parameters.

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

Update 8: New message KO2Z069I (July 2011)


KO2Z069I OMPE V510 The value for the virtual storage limit of the server is MEMLIMIT(%%%%%%%%).

Explanation:

Depending on the specified value for the virtual storage limit of the server, one of the following messages might be displayed:

Not specified:
KO2Z035I OMPE V510 The value for the virtual storage limit of the server is MEMLIMIT(NOLIMIT).

MEMLIMIT=NOLIMIT
KO2Z035I OMPE V510 The value for the virtual storage limit of the server is MEMLIMIT(NOLIMIT).

MEMLIMIT=4M
KO2Z069I OMPE V510 The value for the virtual storage limit of the server is MEMLIMIT(x"00000000_00000004"MB).

The maximum value that can be specified for MEMLIMIT is 2048M.

System Action: None.

User response: None.

------------------------------------------------------------------------
Update 9: New message FPEM0804I in PM44548 (August 2011) and updated messages FPEM0811I and FPEM0819I

FPEM0804I Task stop trigger is: <V1>


Explanation:

<V1> includes the following stop trigger criteria:

  • Stop by timestamp
  • Stop by user request
  • Stop by termination
  • Stop by number of records
  • Stop by IFCID
  • Stop by number of IFCIDs
  • Stop after START TRACE error
  • Stop after READA error
  • Stop after WRITE RECORD error

This message is often accompanied by another message that describes the problem in detail and the appropriate course of action.

FPEM0811I Task start trigger is: <V1>

Explanation:

This message is accompanied by messages FPEM0800I and FPEM0819I.

Depending on one of the following start striggers, DB2 data is collected accordingly:

  • Time: When the user-specified time is met.
  • Periodic Exception: When the Periodic Exception task finds a field that is in exception status, and if this field matches the user-specified field.
  • Exception Event: When the Data Server finds an exception event that matches the user-specified exception event.
  • Immediate Start: Immediately.

FPEM0819I Task description is: <V1>

Explanation:

<V1> is the name of the Collect subtask.

A default name is initially assigned to this subtask. You can change the default name on the main Collect facility menu.

This message is always accompanied by message FPEM0800I.


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

Update 10: New messages FPEA0803I and FPEA0804I (August 2011)

FPEA0803I IFCIDS 233 FOUND IN THE INPUT TRACE ARE USED TO CALCULATE PACKAGE ACTIVITIES. DATA OF SUBPROGRAMS ARE TREATED AS PART OF THE CALLING ACTIVITY.

Explanation:

The IFCIDs are used for the calculation that is requested by the command ORDER(ACTNAME). Stored Procedures and User Defined Functions are clearly identified. The data about subprograms that is called by Stored Procedures and User Defined Funtions is processed as part of the calling routine.


FPEA0804I THE CALCULATION BY ACTIVITY NAME TREATS SUBPROGRAMS AS SEPARATE ACTIVITIES.

Explanation:

The calculation that is requested by the command ORDER(ACTNAME) uses IFCID 3 and IFCID 239. These are the standard accounting IFCIDs. Data about subprograms that is called by an activity is treated as separate activity because the activity type is inherited from DB2.

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

Update 11: New messages KO2X038E, KO2Z643W, KO2Z665W in PM44106 (August 2011)

KO2Z038E OMPE V <%%%%> SSI call failed RC=<%%%%> RSN=<%%%%> SSIRC=<%%%%>

Explanation:

The subsystem service request failed.

System action:

The subsystem function request is rejected with error codes and reason codes.

User response:

Provide the OMPE collector job log and the SVC dump for IBM support.


KO2Z643W OMPE V <%%%%> The XCF requestor is no longer connected. RC=<%%%%> ARSN=<%%%%>

Explanation:

The XCF send service request failed because the service requestor is no longer connected.

System action:

The send service request is rejected.


KO2Z665W OMPE V <%%%%> No collector found on LPAR=<%%%%> to service the XCF request for SSID=<%%%%> RSN=<%%%%>

Explanation:

The send service request cannot be completed because an OMPE cEollector cannot be found on the target LPAR.

System action:

The XCF send service request is rejected.

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

Update 12: New message FPEM0806W in PM46171 (November 2011)


FPEM0806W <V1> records are not written to '<V2>'.
The maximum record length of one of these records is <V3>.

Explanation:

This message shows the number of records that is not written to the output data set.

  • <V1> is the number of records that is not written to the output data set.
  • <V2> is the name of the output data set that is used to collect the trace data.
  • <V3> is the maximum length of the trace data record that is not written to the output data set.

User response:

To write the complete trace data to the output data set, follow these steps:
  1. Allocate a new output data set to collect the trace data.
  2. Increase the record length of the output data set to at least the maximum length of the trace data record that could not be written to the output data set.
  3. Restart the trace.

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

Update 13: New messages FPEV2104I and FPEV2105I in PM52466 (December 2011)

FPEV2104I <V1> EPTT=<F2> (ELAPSED PROCESSING TIME THRESHOLD)

Explanation:

The following list shows the current settings for the elapsed processing time threshold:
  • <V1> is the DB2 subsystem ID.
  • <F2> is the elapsed processing time threshold in seconds .



FPEV2105I <V1> TONT=<F2> (TIMEOUT NOTIFY THRESHOLD)

Explanation:

The following list shows the current settings for the timeout notification threshold:
  • <V1> is the DB2 subsystem ID.
  • <F2> is the timeout notification threshold in seconds.

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

Update 14: New message KO2R0112I in PM52470 and PM52468 (December 2011)

KO2R0112I FORMAT STARTED FOR DATA SET - <Data Set Name>

Explanation:

A new linear data set is formatted so it can be used by the Near Term History collector.

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

Update 15: New messages KO2Z659I and KO2Z662I in PM49637 (February 2012)

KO2Z659I OMPE Vnnn WLM Enclave %%%%%% successful IIPHONORPRIORITY=%%% zIIPs=%%%%%%%%

Explanation:

The zIIP offload WLM enclave is created or deleted. The message field IIPHONORPRIORITY= shows the value that is specified in the IEAOPTxx member of the MVS PARMLIB.
  • If IIPHONORPRIORITY=NO is specified, standard processors do not process zIIP workloads.
  • If IIPHONORPRIORITY=YES is specified, standard processors process zIIP workloads.
The message field zIIPs= shows the number of online zIIP processors that are detected by the OMPE Collector initialization process.

System action:

The initialization of the subsystem continues.


KO2Z662I OMPE Vnnn Common routing table task %%%%%%%%%% AUTOTIME=%%%% ROUT=%%%%%%%%

Explanation:

The message field %%%%%%%%%% shows one of the following status messages:

Initialized
The DB2 routing table is initialized successfully.

Terminated
The virtual storage of the DB2 routing table is released successfully.

Wait-Einit
The initialization of the DB2 routing table is created by PESERVER. AUTOTIME specifies the number of seconds at which the DB2 routing table is refreshed.

The message field ROUT= shows the ECSA virtual storage address of the DB2 routing table.

System action:

The initialization of the subsystem continues.

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

Update 16: New message KO2Z667I in PM55403 (April 2012)

KO2Z667I OMPE V 510 XCF Gateway message ID KO2Z665W suppressed.
LPAR= %%%%%%%% COUNT= %%%%%%%%

Explanation:

The XCF send service request was sent to LPAR %%%%%%%%.
The message ID KO2Z665W was suppressed %%%%%%%% times.

System action:

The XCF send service request is rejected.

User response:

Start the OMEGAMON PE Collector on the target LPAR.

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

Update 17: New message FPEM0807I in PM55120 (April 2012)

FPEM0807I The OP buffer high water mark is <V1>.

Explanation:

DB2 fills the OP buffer that is assigned to the Collect task. The Collect task issues a READA command to read the OP buffer. <V1> is the maximum number of bytes used.
------------------------------------------------------------------------

Update 18: New message KO2H0605I in PM62281 (May 2012)

KO2H0605I <V1> Waiting for initialization of output writer task <V2> minutes.

Explanation:

<V1> is the name of the DB2 subsystem.
<V2> is the number of minutes.

This message might be issued every five minutes. The Near Term History task is waiting for the output writer task to complete the initialization.

System action:

The output writer task might be pre-formatting the VSAM linear data sets or it might be processing the VSAM files.

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

Update 19: New message KO2Z091E in PM68972 (September 2012)

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 20: Addition of new message FPEV1342I (November 2012)

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 21: New messages related to the Spreadsheet Input Data Generator (Dezember 2012)

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

ko2me_fpep.pdfko2me_fpep.pdf

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

Update 22: Changed message KO2Z665W in PM74343 (January 2013)

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 23, 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 24: 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.

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

Publication number

GH12-6923-00

Original publication date

2011/3/8

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

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

Software version:

5.1.0

Operating system(s):

z/OS

Reference #:

7020983

Modified date:

2014-07-29

Translate my page

Machine Translation

Content navigation