RAS1 log files and their locations
The name and location of the agent log files varies on different operating systems.
The RAS1 log files for the monitoring agents are saved in the following directories:
- Windows™ systems: install_dir\tmaitm6\logs\hostname_product_hextimestamp-nn.log
- UNIX™ and Linux™ systems: install_dir/logs/hostname_product_hextimestamp-nn.log
- z/OS® systems: Rklvlog/Rkpdlog
- install_dir is the installation directory of the product.
- hostname is the host name of the computer on which the agent is running.
- product is the two-character product code.
- For IBM MQ Monitoring Agent, the product code is mq.
- For IBM Integration Bus Monitoring Agent, the product code is qi.
- hextimestamp is an eight-character hexadecimal timestamp representing the time at which the agent is started.
- nn is a rolling log suffix.
For example, if a IBM MQ Monitoring Agent is running on an AIX® computer, tivp5glp4, the message log file is created and might be named as tivp5glp4_mq_1375668546.log when the agent is started. The RAS log file for the agent might be named as tivp5glp4_mq_51ff14f0-01.log.
For long-running agents, the nn suffix is used to maintain a short history of log files for that startup of the agent. For example, the IBM MQ Monitoring Agent might have a series of log files as follows:
tivp5glp4_mq_51ff14f0-01.log
tivp5glp4_mq_51ff14f0-02.log
tivp5glp4_mq_51ff14f0-03.log
As the agent runs, the first log (nn=01) is preserved because it contains program startup information. The remaining logs roll. In other words, when the set of numbered logs reach a maximum size, the remaining logs are overwritten in sequence. Each time a agent is started, a new timestamp is assigned to maintain a short agent program history. For example, if the IBM MQ Monitoring Agent is started twice, it might have log files as follows:
server01_mq_437fc59-01.log
server01_mq_437fc59-02.log
server01_mq_437fc59-03.log
server01_mq_537fc59-01.log
server01_mq_537fc59-02.log
server01_mq_537fc59-03.log