IBM Tivoli Monitoring - Log Files
Jim Felder 100000DKPV Visits (1775)
IBM Tivoli Monitoring components produce various log files that contain important information that is especially useful when doing problem determination and problem source identification.
This log contains diagnostic information at the code level. The level of detail is controlled by the value of the KBB_RAS1 environment variable as well as component-level environment variables such as KDC_DEBUG and KDE_DEBUG. Messages show the module name, source line number, and function name that produced the message, for example:
On Windows, UNIX, and Linux systems, the filename is of the form host
where pc is the product code, tttttttt is the Unix time, or POSIX time in hexadecimal when the component opened the log file, and nn is the log file sequence number. The size and number of RAS1 log files is controlled by the KBB_RAS1_LOG environment variable. By default, log file –01 is preserved, while files –02 through –nn wrap when file –nn reaches its maximum size.
When sending in documentation for a problem, it is important to send all RAS1 log files in the set for a complete representation of the state of the component in question.
On z/OS, the RAS1 messages are imbedded in the RKLVLOG data set, described below.
This log, also referred to as the MSG2 log, contains messages related to the operation of the component that produced it. These messages are prefixed by a message identifier, and are described in the IBM Tivoli Monitoring Messages Guide. An example of an operational message produced by the monitoring server is:
Tue Jun 25 10:12:51 2013 KO4SRV032 Tivoli Enterprise Monitoring Server (TEMS) startup complete.
On Windows systems, the filename varies by component. For example, the TEMS operational log file is named KDSMAIN.MSG, and the Windows agent operational log filename is of the form Prim
On UNIX and Linux systems, the filename is of the form host
On z/OS, the operational messages are imbedded in the RKLVLOG data set, described below.
IBM Tivoli Monioring engine log – RKLVLOG – z/OS only
This log contains messages produced by the engine component. Imbedded in the RKLVLOG data set are the RAS1 and operational (MSG2) messages. An example of an engine message is:
2013.179 04:25:45 KLVST045 BASIC SERVICES DRIVER: tms_
IBM Tivoli Monitoring persistent datastore log – RKPDLOG – z/OS only
This log contains messages produced by the persistent datastore component. An example of a persistent datastore component message is:
2013/06/28 04:26:00 KPDMANE: Persistent DataStore facility initializing.
IBM Tivoli Monitoring problem determination data collection tools
The preferred method for collecting problem determination data is by using the tools provided by the product for this purpose. Their goal is to gather appropriate data such that IBM support will be able to have a complete picture of a component and not have to request additional data unless more detailed tracing is required.
In the Windows environment, the utility is named pdcollect.cmd, and in the UNIX/Linux environment it is named pdcollect. When the tool completes, FTP the binary output file to IBM.
In the z/OS environment, the tool is invoked as a CLIST named KMSPDCOL in the RKANSAM data set.
The IBM Tivoli Monitoring Command Reference SC22-5448-00 contains additional information on the pdcollect tool.
The z/OS version of the tool is described by the following web page:
For TEMS issues, the tool should be invoked with the option to collect the QA1 files from the TEMS.