Messages for z/OS components
The Tivoli Enterprise™ Monitoring Server on z/OS® and its various subsystems (OMNIMON, TMS:Engine, and OMEGAMON® base) generate log files that contain messages and trace information. The log files contain message and trace information about the events and processing being performed. z/OS log files provide a complete record of system activity, not just of problems. The log files are created when you start the IBM® Tivoli® Monitoring z/OS components. Table 2 lists the log files created by each z/OS subcomponent. These files are available to help you resolve problems encountered while using the products. IBM Software Support might request some or all of these files while investigating a problem you have reported.
When you encounter a problem, first check the messages in the log files to determine if the source is a problem in the IBM Tivoli Monitoring environment or with an OMEGAMON z/OS monitoring agent. If you determine that the problem is due to a product defect, contact IBM Software Support. IBM Software Support might request that you activate tracing so that the log files collect additional information needed to resolve the problem. Some of the tracing options produce large amounts of trace information. Therefore, monitor the disk or spool space when activating tracing to prevent your disk or spool from reaching capacity. Return the trace settings to the default settings after the desired trace information has been collected. For the locations of various types of logs, see Table 2.
The messages for this product are in two formats. One format includes a single-digit component identifier with a message type and the other includes a double-digit component identifier with no message type. Both formats have the following common elements:
- www
- is the message component
identifier. The usual length of a component identifer is three characters,
though it can be a few as two characters or as many as five. This
book includes the message identifiers in Table 1:
Table 1. Message component identifiers documented in this book Message prefix Components using this prefix CI OMEGAMON Base CND OMEGAMON Base CSA OMEGAMON Base CT OMEGAMON Base ETE™ End-to-End Response Time Monitor IA Classic OMEGAMON IN Classic OMEGAMON KBB Tivoli Management Services: Engine (TMS:Engine) KCN OMNIMON Base KDH TMS:Engine KLB TMS:Engine KLE TMS:Engine C language interface messages KLU Tivoli Enterprise Monitoring Server on z/OS or TMS:Engine KLV Tivoli Enterprise Monitoring Server on z/OS or TMS:Engine KLX Tivoli Enterprise Monitoring Server on z/OS or TMS:Engine KMV OMEGAVIEW® KOB OMEGAMON Base (Enhanced 3270 user interface), Parameter Generator (PARMGEN), or Configuration Manager KPQ OMEGAMON Base (Persistent data store) KSD OMEGAVIEW LSC Classic OMEGAMON OB OMEGAMON Base OM OMEGAMON Base - yyy
- Message number.
wwwxxyyy
- x
- Component identifier.
- yyy
- Message number.
- z
- One-letter message type. Some messages have this message type
indicator. It can be one of the following:
- I for informational messages, which typically do not require administrator or operator actions.
- W for warning messages, which typically require actions.
- E for error messages, which indicate a problem that you must resolve before normal operation can continue.
In the message description, most message headings are self-explanatory (for example, Explanation or System Response). Some messages include a heading for Severity. Severity is sometimes defined as a number between 0 and 80, where 0 means it is unimportant and 80 means the matter requires immediate attention. This numerical value is often paired with a system programmer response heading, so that you know how to respond to the severity indicator.
- REPLY, VIEW or INFO: indicates successful completion or attempted completion of an request.
- ERROR: indicates that a system action has failed to complete successfully.
- WARNING or ALERT: indicates that an error has occurred and offers additional details to help you correct the problem that often involves contacting IBM Software Support.
- ABEND: reports a component failure that requires immediate system programmer response and usually requires running traces and collecting dumps for IBM Software Support.
- FATAL: indicate a condition causing shutdown or catastrophic termination.
Messages with severity tags can sometimes be routed to different console groupings. When the Severity tag is used to described TMS:Engine errors, the value indicates where the message will be sent. For more information, see TMS:Engine message route codes.
Table 2 contains the locations of logs where distributed component messages are found:
| z/OS component | Log location |
|---|---|
| An OMEGAMON monitoring agent on z/OS | RKLVLOG for the monitoring agent started task is the single most helpful piece of service information for an OMEGAMON monitoring agent on z/OS. The RKLVLOG (R = runtime, KLV = the prefix associated with IBM Tivoli Monitoring Services:Engine or TMS:Engine) is the sysout data set or spool file that contains log and trace messages. These additional zSeries® log files (if available) are also
useful:
Note: OMEGAMON monitoring agent on z/OS messages are documented in the agent-specific problem
determination guide. |
| Tivoli Enterprise Monitoring Server on z/OS |
RKLVLOG for the monitoring agent started task is the single most helpful piece of service information for an OMEGAMON monitoring agent on z/OS. The RKLVLOG (R = runtime, KLV = the prefix associated with IBM Tivoli Monitoring Services:Engine or TMS:Engine) is the sysout data set or spool file that contains log and trace messages. These additional zSeries log files (if available) are
also useful:
Note: OMEGAMON monitoring agent on z/OS messages are documented in the agent-specific problem
determination guide. Because the Tivoli Enterprise Monitoring Server on z/OS runs under TMS:Engine just as an OMEGAMON monitoring agent on z/OS does,
all logging under TMS:Engine is handled the same way, that is log and trace data are written to
RKLVLOGs and RKPDLOGs. |
| ETE | ETE is
a base component and does not have its own RKLVLOG. This component
writes messages to the IBM System
Display and Search Facility (SDSF) Job Log. The User Response section
of various ETE message requests
that you collect systems information and memory dumps before contacting IBM Software Support. How to collect
this information for ETE is documented
in the IBM Tivoli End to End Response Time Reference book. Note: ETE messages are documented in the IBM Tivoli End
to End Response Time Reference book. |
| IBM Tivoli Management Services: Engine (TMS:Engine) | TMS:Engine is a collection of basic operating system and communication service routines built specifically for z/OS. All address spaces used by OMEGAMON monitoring agents on z/OS load and use the services of TMS:Engine. Successful initialization of TMS:Engine is noted by this message: TMS:Engine writes messages to the same RKLVLOG as the product it is running. If you search the RKLVLOG for an OMEGAMON monitoring agent on z/OS, product-specific messages start with the product code (for example, KN3 for OMEGAMON for Networks on z/OS) but messages for the TMS:Engine start with component prefixes KBB, KDH, KLB, KLE, KLU, KLV, and KLX. |
| OMEGAMON subsystem | The OMEGAMON subsystem does not allocate an RKLVLOG. This component issues messages directly to the z/OS system console (or SYSLOG). |
| Persistent data store | The RKPDLOG sysout data set or spool file contains the information and error messages related to the handling of persistent data stores. |