Problems affecting an OMEGAMON Monitoring Agent on z/OS

Most problems that appear in the Tivoli® Enterprise Portal does not mean that the component is the source of the failure. You can check the locations of log and trace information for z/OS components to troubleshoot the problems.

After you have ruled out problems with the IBM® Tivoli Management Services components and the functionality for which you installed an OMEGAMON Monitoring Agent on z/OS is not available, then treat the problem as a monitoring agent problem. Most monitoring agent problem determination guides include chapters for these types of problems:

Installation and configuration
Data collection
Performance
Usage

A data collection problem with a monitoring agent manifests itself as the display of no data or incorrect data in Tivoli Enterprise Portal.

Log files and trace information are provided in a common way across all OMEGAMON Monitoring Agent on z/OS and the z/OS components of the Tivoli Management Services.

Table 4 explains the location of log and trace files for an OMEGAMON Monitoring Agent on z/OS and Tivoli Management Services z/OS components.

Table 1. Locations of log and trace information for z/OS components
Component	Description
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 dataset or spool file that contains log and trace messages. Instructions on how to save the contents of this log to a dataset are provided under Capturing z/OS logs to send to IBM Software Support. These additional zSeries log files (if available) are also useful: The RKLVSNAP sysout dataset or spool file contains formatted dump output. The RKPDLOG sysout dataset or spool file contains the information and error messages related to the handling of persistent data stores. Refer to your started procedures for the locations of these serviceability log files.
Tivoli Enterprise Monitoring Server on z/OS®	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.
IBM Tivoli Monitoring 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 Agent on z/OS load and use the services of TMS: Engine. Successful initialization of TMS: Engine is noted by this message: `KLVIN408 IBM OMEGAMON PLATFORM ENGINE VERSION 400 READY` For troubleshooting information about TMS: Engine problems, refer to the z/OS initialization section of the IBM Tivoli Monitoring Troubleshooting Guide. Explanations for messages generated by TMS: Engine can be found in IBM Tivoli Monitoring: Messages. TMS: Engine writes messages to the same RKLVLOG as the product it is running. If you search the RKLVLOG for a OMEGAMON Monitoring Agent on z/OS, product-specific messages start with the product code (for example, KS3 for OMEGAMON® for Storage) but messages for the TMS: Engine start with that component prefix, KLV.
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 dataset or spool file contains the information and error messages related to the handling of persistent data stores. To dump this log, follow the procedures described for RKLVLOG in the sections that follow.

For locations of log files for all the components of Tivoli Management Services and information about enabling tracing for distributed components, refer to the IBM Z OMEGAMON AI for Storage: Troubleshooting Guide.