Setting up RAS1 tracing

RAS1 is the OMEGAMON component that provides trace and dump routines.

RAS1 tracing provides runtime filtering of product messages and is the primary diagnostic tool for OMEGAMON. It is provided by the kbb library service and is set using either the IBM® Tivoli® Monitoring Service Console interface or some more direct method of manually modifying the KBB_RAS1 parameter. You must send the RAS1 messages to stdout, so that one of the components in the configurator programs redirects that output to the files shown in Table 4.

Not all OMEGAMON products or functions support RAS1 tracing, and neither do they use the filters and classes in the same way. For example, two monitoring agents might use the filters and classes specified in RAS1 tracing differently and with different frequencies.

Again, 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.