RAS1 Tracing for the OMEGAMON Subsystem

You can start and stop tracing for the OMEGAMON Subsystem.

Note: Tracing can cause excessive output to the Tivoli OMEGAMON Manager job log. Consult IBM Software Support for advice before you enable tracing.

Tracing for the OMEGAMON Subsystem is dynamically started and stopped using modify commands. Trace messages are produced in the OMEGAMON Subsystem's SYSPRINT location, the SYSTRACE DD location, or both. For example:

/F IBMCN,TRACE KOBHTTPW 1

You can initiate tracing for one or more components at startup by adding a TRACEV1 statement in the OMEGAMON Subsystem's RKANPARU(KOBENV) member and specifying a component (or components) and level of tracing.

For example:

TRACEV1=TRACE KOBxxxxx n

where:

The variable n is the trace level, and has a value of 0 - 4. A trace level of 0 indicates that no tracing takes place and disables tracing if it was already enabled. A trace level of 1 - 4 enables tracing; 1 generates the least number of trace messages, while 4 generates the most trace messages.

The value of KOBxxxxx is as follows:

KOBHTTPS KOBHTTPL KOBHTTPW KOBHTTP$ KOBHTTP@ KOBHTTP# KM5JLFRD

Note: Tracing can be dynamically turned off by issuing a modify command with a value of 0 for the trace level. For example:

/F IBMTOM,TRACE KOBHTTPW 0

Multiple components can be specified on the TRACEV1 statement. For example:

/F IBMTOM,TRACE KOBHTTPW 1, KOBHTTPS 2

Be sure to comment or remove the TRACEV1 statement in the KOBENV member when debug messages are no longer needed.