Tivoli Enterprise Monitoring Server

The location of logs for a Tivoli® Enterprise Monitoring Server is different in Windows and Unix-based systems.

For the location of logs for a Tivoli Enterprise Monitoring Server on z/OS®, see Problems reported as Tivoli Enterprise Portal Server problems.

Table 1. Log locations for Tivoli Enterprise Monitoring Server on distributed platforms
Component Windows UNIX-based
Tivoli Enterprise Monitoring Server

install_dir\logs\hostname_PC_

HEXtimestamp-nn.log

where:

install_dir

Specifies the directory where Tivoli Enterprise Monitoring Server was installed.

PC

Specifies the product code. ms for Tivoli Enterprise Monitoring Server.

HEXtimestamp

A hexadecimal representation of the time at which the process was started.

nn

Represents the circular sequence in which logs are rotated. Ranges from 1-5, by default, though the first is always retained, since it includes configuration parameters.

install_dir/logs/hostname_PC_

timestamp.log

where:

install_dir

Specifies the directory where Tivoli Enterprise Portal Server was installed.

hostname

Specifies the name of the system hosting the product.

PC

Specifies the product code. cq for the Tivoli Enterprise Portal Server.

timestamp

A decimal representation of the time at which the process was started.

Tivoli Enterprise Monitoring Server operations logs

Use the operations logs to determine the cause of problems. IBM® Tivoli MonitoringIBM Tivoli Monitoring operations logging replaces MSG2 logging. The new optional logs replace the Tivoli Enterprise Monitoring Server log files \install_dir\cms\kdsmain.msg on Windows systems and install_dir/logs/hostname_ms_timestamp.log on UNIX-based systems.

To use the new logging facility for the Tivoli Enterprise Monitoring Server, modify the \install_dir\cms\KBBENV file on Windows systems or the install_dir/config/hostname_ms_TEMS ID.config file and install_dir/config/kbbenv.ini file on UNIX-based systems. Add the following line to the file:

MSG_MODE=kms

To disable the new logging facility and return to original logging, either remove this line in the file or change it to:

MSG_MODE=MSG2