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

Manual


Abstract

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

Content

This manual includes the following updates:

  • Update 1: New and modified DGOK7xx messages in UK48370 (July 2009)
  • Update 2: New KO2E3xx message in PK90683 (August 2009)
  • Update 3: New and modified FPEV0xx messages in PK93600 and PK93794 (August 2009)
  • Update 4: Modified user response for message FPEV0560E in PK97285 (October 2009)
  • Update 5: Modifications to KO2O092xE messages in PK86834 (November 2009)
  • Update 6: New message KO2O1165W in PK87781 (December 2009)
  • Update 7: New message KO2O1294E in PK78190 (June 2010)
  • Update 8. New messages FPEV0273I, ...74E, ...75E in PM17339 (July 2010)
  • Update 9: Modification to message FPEV0187I in PM07261 (August 2010)
  • Update 10: Added missing message FPEV3016W (September 2010)
  • Update 11: New FPEV21xx and modified FPEV3013E messages in PM21372 (November 2010)
  • Update 12: New message FPEC4004E in PM24117 (March 2011)
  • Update 13: New messages KO2Z663I and KO2Z664I in PM36656 (July 2011)
  • Update 14: New message FPEM0804I in PM41324 (August 2011) and updated messages FPEM0811I and FPEM0819I
  • Update 15: New message FPEM0806W in PM46171 (November 2011)
  • Update 16: New message KO2O0602W in PM44822 (November 2011)
  • Update 17: New message KO2Z667I in PM55403 (April 2012)
  • Update 18: New message KO2O1369I in PI05484 (February 2014)



Update 1: New and modified DGOK7xx messages in UK48370 (July 2009)


DGOK704 DB2 Visual Explain, Optimization Service Center for DB2 for
z/OS, DB2 Optimization Expert for z/OS, or Optim Query Tuner
Client is not installed.

Explanation:

DB2 Visual Explain, Optimization Service Center for DB2 for z/OS, DB2
Optimization Expert for z/OS, or Optim(TM) Query Tuner Client needs to
be installed to use the Explain functionality.

User response:

Install one of these products and restart DB2 Performance Expert Client.

------------------------------------------------------------------------
DGOK712 Visual Explain installation detected but not supported for DB2
V9 and above.

Explanation:

Visual Explain is only supported for DB2 V8 and below.

User response:

Install Optimization Service Center for DB2 for z/OS, DB2 Optimization
Expert for z/OS, or Optim Query Tuner Client.

------------------------------------------------------------------------
DGOK713 Optim Query Tuner Client not started.

Explanation:

The Optim Query Tuner Client is installed but not started. You need to
start the client to explain the SQL Statement.

User response:

Start the Optim Query Tuner Client.

------------------------------------------------------------------------
DGOK714 Exception encountered during Optim Query Tuner Client usage.

Explanation:

An internal exception occurred.

User response:

Contact IBM support.

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

Update 2: New KO2E3xx message in PK90683 (August 2009)


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: New and modified FPEV0xx messages in PK93600 and PK93794 (August 2009)


FPEV0080I <V1> DB2 SUBSYSTEM <V2> STOPPED <V3>

Explanation:

This message is self-explanatory.
* <V1> is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <V2> is the DB2 subsystem ID.
* <V3> is the reason for the DB2 subsystem to stop:

QUIESCE Normal stop of the DB2 subsystem. Current threads can run to
completion, and new threads can be allocated to an
application that is running.
FORCE Normal stop of the DB2 subsystem. No new threads are
allocated, and work on existing threads is rolled back.
ABTERM Abnormal stop of the DB2 subsystem.

User response:

None.

------------------------------------------------------------------------
FPEV0081I <V1> DB2 SUBSYSTEM <V2> STARTED

Explanation:

This message is self-explanatory.
* <V1> is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <V2> is the DB2 subsystem ID.

User response:

None.

------------------------------------------------------------------------
FPEV0187I <V1> - <Name> <Status> <Detected> <Lvl> <Location> <Type>
<Dsg> <Lpar>

Explanation:

This message is issued in response to a DISPLAY command or during
OMEGAMON Collector startup. It indicates that the specified DB2
subsystem was auto-detected at the LPAR and is monitored with limited
functionality.
* <V1> is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <Name> is the DB2 subsystem ID.
* <Status> is the monitoring status of the DB2 subsystem, which can be
one of the following:

INITIAL The DB2 subsystem is known to the OMEGAMON Collector, but
there is neither a connection established nor a monitoring
subtask started yet.
UP The DB2 subsystem is running, but the subtask that monitors
this DB2 subsystem is not yet started.
MONITORED
The DB2 subsystem is monitored.
DOWN The DB2 subsystem is not running.
DENIED The OMEGAMON Collector started task user ID does not have
the required privileges to connect (IDENTIFY) to this DB2
subsystem.
IGNORED The version of this DB2 subsystem is not supported.
Therefore, this DB2 subsystem cannot be monitored.
EXCLUDED The DB2 subsystem is excluded from monitoring. This happens
in the following cases:
* The indicated DB2 subsystem was marked in the
Configuration Tool as not to be monitored.
* Monitoring of the indicated DB2 subsystem was stopped by
an operator command.
* The monitoring subtask stopped because of a problem.

For other possible reasons check the SYSPRINT for messages
that explain why the DB2 subsystem is not monitored.

MONDSG The indicated DB2 subsystem is monitored implicitly. The DB2
subsystem is a local member of a data sharing group that is
excluded from monitoring (configuration) or it is not
configured while AUTODETECT is disabled. The DB2 subsystem
is monitored implicitly by another local data sharing group
member without starting any additional subtasks for
monitoring this DB2 subsystem.
UNKNOWN The status of the DB2 subsystem cannot be determined for one
of the following reasons:
* The DB2 subsystem is a remote member of a data sharing
group and no local member of the data sharing group is
currently monitored. Therefore, no information about the
DB2 subsystem can be obtained.
* The DB2 subsystem is a local member of a data sharing
group that is excluded from monitoring (configuration) or
it is not configured while AUTODETECT is disabled. This
DB2 subsystem can be monitored implicitly by another
local data sharing group member without starting
additional subtasks for monitoring this DB2 subsystem. If
explicit monitoring of all local data sharing group
members is stopped, no implicit monitoring is possible,
and therefore, no information can be obtained for local
and remote members of the data sharing group.

* <Detected> indicates whether the DB2 subsystem was found by means of
auto-detection.

Y This DB2 subsystem was auto-detected.
N This DB2 subsystem was configured explicitly or is a remote
or implicitly monitored data sharing group member.
* <Lvl> indicates the DB2 version, release, and modification level as a
three-digit character string.
* <Location> indicates where the DB2 subsystem is running.

LOCAL The DB2 subsystem runs in the same LPAR as the OMEGAMON
Collector.
REMOTE The DB2 subsystem is a data sharing group member that does
not run on the same LPAR as the OMEGAMON Collector.
* <Type> indicates the type of the DB2 subsystem.

SINGLE The DB2 subsystem does not run in a data sharing group
environment.
MEMBER The DB2 subsystem is a member of a data sharing group.
* <Dsg> The name of the data sharing group to which this DB2 subsystem
belongs.
* <Lpar> indicates the name of the z/OS system where the member is
running or was last running before monitoring stopped.

User response:

If the status is DENIED, contact your security administrator and request
authority for the OMEGAMON Collector to access this DB2 subsystem.

------------------------------------------------------------------------
FPEV0188I <V1> <DB2_ID> <Status> <Detected> <Lvl> <Location> <Type>
<Dsg> <Lpar>

Explanation:

This message is issued in response to a DISPLAY command or during
OMEGAMON Collector startup. It indicates that the specified DB2
subsystem was specified in the list of DB2 subsystems (parameter
DB2SSID) to be monitored.
* <V1> is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <DB2_ID> is the DB2 subsystem ID.
* <Status> is the monitoring status of the DB2 subsystem.
* <Detected> indicates whether the DB2 subsystem was found by means of
auto-detection.
* <Lvl> indicates the DB2 version, release, and modification level as a
three-digit character string.
* <Location> indicates where the DB2 subsystem is running.
* <Type> indicates whether the DB2 subsystem is a member of a data
sharing group.
* <Dsg> is the name of the data sharing group to which this DB2
subsystem belongs.
* <Lpar> is the name of the z/OS system where the member is running.

See message FPEV0187I for details.

User response:

None.

------------------------------------------------------------------------
FPEV0224I <V1> INSTANCE FOR DB2 SUBSYSTEM <V2> STOPPED

Explanation:

The OMEGAMON Collector components that monitor the indicated DB2
subsystem have been stopped.
* <V1>is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <V2> is the DB2 subsystem ID.

User response:

None.

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

Update 4: 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 5: 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 6: 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 7: 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.

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


Update 8. New messages FPEV0273I, ...74E, ...75E in PM17339 (July 2010)


FPEV0273I <V1> PARAMETER DATASET MEMBER <V2> NOT FOUND. MONITORING FOR
DB2 SUBSYSTEM <V3> IS ENABLED WITH LIMITED FUNCTIONALITY

Explanation:

During OMEGAMON Collector startup a DB2 subsystem was automatically
detected and a PE Server subtask was started to monitor the DB2
subsystem. The corresponding parameter dataset member could not be
found. Monitoring for the DB2 subsystem is enabled with limited
functionality. Only realtime monitoring without DB2 Connect monitoring
is supported.
* <V1> is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <V2> is the name of the RKD2PAR parameter dataset member.
* <V3> is the DB2 subsystem ID.

User response:

None, if realtime monitoring with limited functionality is desired.
Otherwise, configure the indicated DB2 subsystem with the Configuration
Tool (formerly ICAT), complete the configuration and restart the
OMEGAMON Collector.

------------------------------------------------------------------------
FPEV0274E <V1> PARAMETER DATASET MEMBER <V2> NOT FOUND. MONITORING FOR
DB2 SUBSYSTEM <V3> IS DISABLED

Explanation:

During OMEGAMON Collector startup a PE Server subtask was started to
monitor a configured DB2 subsystem, or a Modify command was issued to
explicitly start a PE Server subtask. The corresponding parameter
dataset member could not be found for a configured DB2 subsystem. The
configuration of the OMEGAMON Collector is not complete. Monitoring for
the DB2 subsystem is disabled.
* <V1> is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <V2> is the name of the RKD2PAR parameter dataset member.
* <V3> is the DB2 subsystem ID.

User response:

Configure the indicated DB2 subsystem with the Configuration Tool
(formerly ICAT), complete the configuration and restart the OMEGAMON
Collector.

------------------------------------------------------------------------
FPEV0275E <V1> ERROR WHEN PREPARING PE SERVER SUBTASK. MONITORING FOR
DB2 SUBSYSTEM <V2> IS DISABLED

Explanation:

During OMEGAMON Collector startup the preparation for the attach of a PE
Server subtask failed. Monitoring for the DB2 subsystem is disabled.
* <V1> is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <V2> is the DB2 subsystem ID.

User response:

Check the job log for preceding error messages, correct the reported
errors and restart the OMEGAMON Collector.

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


Update 9: Modification to message FPEV0187I in PM07261 (August 2010)


FPEV0187I <V1> - <Name> <Status> <Detected> <Lvl> <Location> <Type>
<Dsg> <Lpar>

Explanation:

This message is issued in response to a DISPLAY command or during
OMEGAMON Collector startup. It indicates that the indicated DB2
subsystem was auto-detected at the LPAR and is monitored with limited
functionality.
* <V1> is the name of the master controller inside the OMEGAMON
Collector (MSTR).
* <Name> is the DB2 subsystem ID.
* <Status> is the monitoring status of the DB2 subsystem, which can be
one of the following:

DENIED The OMEGAMON Collector started task user ID does not have
the required privileges to connect (IDENTIFY) to this DB2
subsystem.
DOWN The DB2 subsystem is not running.
EXCLUDED The DB2 subsystem is excluded from monitoring. This happens
in the following cases:
* The indicated DB2 subsystem was marked in the
Configuration Tool as not to be monitored.
* Monitoring of the indicated DB2 subsystem was stopped by
an operator command.
* The monitoring subtask stopped because of a problem.

For other possible reasons check the SYSPRINT for messages
that explain why the DB2 subsystem is not monitored.

IGNORED The version of this DB2 subsystem is not supported.
Therefore, this DB2 subsystem cannot be monitored.
INITIAL The DB2 subsystem is known to the OMEGAMON Collector, but
there is neither a connection established nor a monitoring
subtask started yet.
MONITORED
The DB2 subsystem is monitored.
MONDSG The indicated DB2 subsystem is monitored implicitly. The DB2
subsystem is a local member of a data sharing group that is
excluded from monitoring (configuration) or it is not
configured while AUTODETECT is disabled. The DB2 subsystem
is monitored implicitly by another local data sharing group
member without starting any additional subtasks for
monitoring this DB2 subsystem.
RESTRICT The DB2 subsystem is known to the OMEGAMON Collector, but
the OMEGAMON Collector is not authorized to connect to the
DB2 subsystem because the DB2 subsystem is started in
restricted access mode (maintenance).
UNKNOWN The status of the DB2 subsystem cannot be determined for one
of the following reasons:
* The DB2 subsystem is a remote member of a data sharing
group and no local member of the data sharing group is
currently monitored. Therefore, no information about the
DB2 subsystem can be obtained.
* The DB2 subsystem is a local member of a data sharing
group that is excluded from monitoring (configuration) or
it is not configured while AUTODETECT is disabled. This
DB2 subsystem can be monitored implicitly by another
local data sharing group member without starting
additional subtasks for monitoring this DB2 subsystem. If
explicit monitoring of all local data sharing group
members is stopped, no implicit monitoring is possible,
and therefore, no information can be obtained for local
and remote members of the data sharing group.

UP The DB2 subsystem is running, but the subtask that monitors
this DB2 subsystem is not yet started.
* <Detected> indicates whether the DB2 subsystem was found by means of
auto-detection.

Y This DB2 subsystem was auto-detected.
N This DB2 subsystem was configured explicitly or is a remote
or implicitly monitored data sharing group member.
* <Lvl> indicates the DB2 version, release, and modification level as a
three-digit character string.
* <Location> indicates where the DB2 subsystem is running.

LOCAL The DB2 subsystem runs in the same LPAR as the OMEGAMON
Collector.
REMOTE The DB2 subsystem is a data sharing group member that does
not run on the same LPAR as the OMEGAMON Collector.
* <Type> indicates the type of the DB2 subsystem.

SINGLE The DB2 subsystem does not run in a data sharing group
environment.
MEMBER The DB2 subsystem is a member of a data sharing group.
* <Dsg> The name of the data sharing group to which this DB2 subsystem
belongs.
* <Lpar> indicates the name of the z/OS system where the member is
running or was last running before monitoring stopped.

User response:

If the status is DENIED, contact your security administrator and request
authority for the OMEGAMON Collector to access this DB2 subsystem.

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


Update 10: Added missing message FPEV3016W (September 2010)


FPEV3016W <V1> NO PATH TO THE PE SERVER INSTANCE FOUND BECAUSE NO
ACTIVE PE SERVER INSTANCE IS AVAILABLE.

Explanation:

A user interface requests performance data for a specified DB2
subsystem. The PE Server receives the request and tries to route the
request to a monitoring PE Server subtask. In a data sharing group a PE
Server subtask must be started for at least one member that resides on
the same LPAR as the OMEGAMON Collector (called local member) to be able
to monitor members of the data sharing group. The data retrieval request
fails if no PE Server subtask is started for the specified DB2 subsystem
or a local member of the data sharing group.
* <V1> is the DB2 subsystem ID.

User response:

Configure the indicated DB2 subsystem or a local member of the data
sharing group with the Configuration Tool (formerly ICAT), complete the
configuration and restart the OMEGAMON Collector. When the indicated DB2
subsystem or local member of the data sharing group has already been
configured or the DB2 subsystems shall be auto-detected, check the
OMEGAMON started task job log for preceding error messages during PE
Server subtask start up, PE Server subtask termination or the occurrence
of an abend. Restart the PE Server subtask. If the problem persists,
contact IBM support.

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


Update 11: New FPEV21xx and modified FPEV3013E messages in PM21372 (November 2010)


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

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

FPEV3013E <V1> <V2> 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.
* <V2> is the date and time when the timeout occurred.

User response:

Resubmit the request. If the problem persists, contact IBM support.

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

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


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 13: New messages KO2Z663I and KO2Z664I in PM 36656 (July 2011)


KO2Z663I OMPE Vnnn The PESERVER subtask DGOVMSTR restarted successfully.
RC=%%%% RSN=%%%% TCB=%%%%

Explanation:

The PESERVER master subtask failed because DB2 stopped.
The PESERVER master subtask restarted successfully.

System action: None.

User action: None.

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


KO2Z664I OMPE Vnnn The PESERVER subtask DGOVMSTR completed successfully.

Explanation: The PESERVER master subtask completed successfully.

System action: None.

User response: None.

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

Update 14: New message FPEM0804I in PM41324 (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 15: 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 16: New message KO2O0602W in PM44822 (November 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 17: 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 18: 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

GC19-2506-00

Original publication date

2009/6/9

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:

4.2.0

Operating system(s):

z/OS

Reference #:

7016286

Modified date:

2014-02-13

Translate my page

Machine Translation

Content navigation