When you have enabled the new logging facility, the Tivoli Enterprise Monitoring
Server writes a new log file: install_dir/itmLogs/itmc_hostname_kms.log. The
Tivoli Enterprise Portal Server also writes to a new file: install_dir/itmLogs/
itmc_hostname_kcq.log.
The properties file (install_dir/itmLogs/itmc_kms.properties for the Tivoli
Enterprise Monitoring Server and the install_dir/itmLogs/itmc_kcq.properties
file for the Tivoli Enterprise Portal Server) determines the maximum size and the
number of rolling log files. The default is 100000 bytes per file and 3 files.
You can modify these values by changing these parameters in the properties file:
fh.maxFileSize=1000000 fh.maxFiles=3. When the log file exceeds the maxFileSize,
the file moves to a new name, for example, itmc_hostname_kms1.log, and new
messages are then written to the original file name, for example,
itmc_hostname_kms.log. The process continues for the number of maxFiles.
z/OS systems
About this task
To use the new logging facility for the Tivoli Enterprise Monitoring Server, modify
the RKANPARU member. 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
The number of log datasets is determined by how many datasets are defined in the
Tivoli Enterprise Monitoring Server JCL procedure. The amount of data that can be
written to each dataset depends on the amount of space allocated at the time each
dataset is created.
To use IBM Tivoli Monitoring Operations Logging on z/OS systems, complete the
following procedure:
1. Create the log datasets. You must create at least one to use the new logging
facility, but it is best to create three. The only limit to the number of datasets
that you create is the limit imposed by the system (typically, about 70). Each
dataset must reside on a disk device. The DCB attributes are DSORG=PS,
RECFM=VB, LRECL=256. The BLKSIZE specification must be at least 260, but
you can allow it to default to the system-determined value for best
performance. The amount of space allocated to the datasets is not critical.
Allocating five 3390 cylinders allows space for about 50000 log records. (The
number varies, depending on the lengths of the messages.)
Note: Do not specify secondary allocations. Any secondary allocations are
ignored.
2. Edit your Tivoli Enterprise Monitoring Server JCL procedure (typically named
CANSDSST, but can be named otherwise). For each of your datasets, add a DD
statement with the DDNAME "RKMSLGnn" that points to the dataset with
DISP=SHR. The first dataset should use "RKMSLG00" as the DDNAME, with
"nn" incrementing by one for each additional dataset.
Note: DO NOT SKIP VALUES of "nn." If any values are skipped, subsequent
OpsLog DD statements are ignored.
62 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
