RAS1 tracing

RAS1 tracing provides runtime filtering of product messages and is the primary diagnostic tool for OMEGAMON. When the Tivoli Management Services z/OS® components are initialized, RAS1 service initialization is one of the first processes started. RAS logs are in the English language only. The RAS trace log mechanism is available on the Tivoli Enterprise Monitoring Server, the Tivoli® Enterprise Portal Server, and the monitoring agents. Most logs are located in a logs subdirectory on the host computer.

RAS1 tracing is provided by the KBB library service. You can set RAS1 tracing either through the trace options file (KppENV) or through the IBM® Tivoli Monitoring Service Console, where pp is the two-letter prefix associated with the monitoring agent, such as MQ for the IBM MQ Monitoring Agent. Tracing enabled through the KppENV file requires the product to be recycled. Tracing enabled through Service Console is dynamic, which does not require recycling. Previously, the Service Console can only be accessed through a browser. However, starting with version 7.3, you can now access the Service Console through the enhanced 3270 user interface.

For most monitoring agents, the KBB_RAS1=ERROR trace level is set by default. You can change this trace level in a number of ways.

Be aware that RAS1 tracing log files can grow very large with the wrong amount of filtering. There is no log management function or feature, so be careful with the levels of tracing that you specify. You might want to run error tracing for all components and then any additional levels depending on diagnostic needs.