Messages shared by distributed and z/OS components

Because the Tivoli Enterprise Monitoring Server can run on both distributed platforms and z/OS®, this component has some messages that can appear in both distributed logs and in the RKLVLOG on z/OS. These shared Tivoli Enterprise Monitoring Server messages can have the following prefixes:

Table 1 shows the locations of logs for Tivoli Enterprise Monitoring Server on distributed platforms and z/OS.

Table 1. Log locations for the Tivoli Enterprise Monitoring Server
Component	Windows systems	UNIX-based systems
Tivoli Enterprise Monitoring Server on a distributed platform message logs	`\install_dir\cms\kdsmain.msg` Where install_dir specifies the directory where Tivoli Enterprise Portal Server was installed.	`install_dir/logs/hostname _ms_timestamp.msg` Where: install_dir Specifies the directory where Tivoli Enterprise Portal Server was installed. hostname Specifies the name of the system hosting the product ms Indicates that these messages are for the Tivoli Enterprise Portal Server. timestamp A decimal representation of the time at which the process was started.
Tivoli Enterprise Portal Server on a distributed platform trace logs	`\install_dir\logs\ kfwservices.msg` Where: install_dir Specifies the directory where Tivoli Enterprise Portal Server was installed.	`install_dir/logs/ kfwservices.msg` Where: install_dir Specifies the directory where Tivoli Enterprise Portal Server was installed.
Tivoli Enterprise Monitoring Server on z/OS	RKLVLOG for the Tivoli Enterprise Monitoring Server on z/OS is the single most helpful piece of service information available for the monitoring server. The RKLVLOG (R = runtime, KLV = the prefix associated with 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: The RKLVSNAP sysout data set or spool file contains formatted dump output. The RKPDLOG sysout data set or spool file contains the information and error messages related to the handling of persistent data stores. The RKPDOUT contains KPDXTRA log messages for debugging persistent data store problems. The JES2 and JES3 system log contains information about JES issues. Refer to your JCL started task procedures for the locations of these serviceability log files.