Message log locations

The OMEGAMON AI for CICS monitoring and CICSplex agents generate log files that contain messages and trace information. The log files contain message and trace information about the events and processing being performed.

The OMEGAMON log files provide a record of system activity, not just a record of problems. The log files are created when you start the OMEGAMON components.

When you have a problem, first check the messages in the log files to determine if the source is a problem in your environment or with an OMEGAMON product. If you determine that the problem is due to a product defect, refer to "Support Information" on how to proceed to 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 huge 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.

Expected failures on the z/OS® operating system are recorded as external messages located in the RKLVLOG file and RKGWSLOG file of the agent address space or Tivoli Enterprise Monitoring Server. Unexpected errors which result in product failure are accompanied with software dumps, traces, or logs. Additional tracing and debugging methods may also be available depending on the failed component.

The statistics component, Statistical Application Programming Interface (SAPI) for the OMEGAMON AI for CICS TG component, and the transaction monitoring component provide their own set of messages, logs, and traces. The destination of standard messages can be either to the system ('WTO') or the RKGWSLOG file ('LOG') and is specified using the KGW_SAPI_CLIENT_MESSAGES_SYSOUT parameter in PARMGEN.. The RKGWSLOG file is dynamically allocated if no RKGWSLOG DD statement is specified in the JCL.

The OMEGAMON AI for CICS TG component monitoring exit (TxnMonitor) provides its own set of log and trace messages that are issued within the address space of the monitored CICS® TG. If this is a Gateway daemon, the messages are written to the STDERR file by default. If this is a WebSphere® Application Server instance, the messages are written to the SYSPRINT file of the SERVANT region by default.

For more information about message logs for components, see IBM Tivoli Monitoring: Troubleshooting Guide.