4. Can trace logs reveal details about the problem?

Your answer:	Do this next:
No	Trace logs frequently reveal the source of a problem. However, if you are certain that trace logs cannot help you, go to Step 7. Is the problem solved?.
Yes	Read about logging in Sources of troubleshooting data for OMEGAMON® for Storage on z/OS®. Set up trace logs for the affected component. Also see Chapter 1, General troubleshooting for the OMEGAMON XE Monitoring Agent on z/OS, for information on these topics: Locations of IBM Tivoli Monitoring trace logs. Locations of trace logs for a specific monitoring agent. Setting up RAS1 tracing, interpreting those logs, and sending logs to IBM Software Support. Setting up OMEGAMON debugging logs, interpreting those logs, and sending logs to IBM Software Support. Note: The unique utilities in OMEGAMON for Storage on z/OS, such as the Storage Toolkit and Dataset Attribute Database, log their messages to the Tivoli Enterprise Portal log. Consult the Tivoli Enterprise Portal log when you are troubleshooting these utilities.

Your answer:

Do this next:

Trace logs frequently reveal the source of a problem. However, if you are certain that trace logs cannot help you, go to Step 7. Is the problem solved?.

Yes

Read about logging in Sources of troubleshooting data for OMEGAMON® for Storage on z/OS®. Set up trace logs for the affected component. Also see Chapter 1, General troubleshooting for the OMEGAMON XE Monitoring Agent on z/OS, for information on these topics:

Locations of IBM Tivoli Monitoring trace logs.
Locations of trace logs for a specific monitoring agent.
Setting up RAS1 tracing, interpreting those logs, and sending logs to IBM Software Support.
Setting up OMEGAMON debugging logs, interpreting those logs, and sending logs to IBM Software Support.

Note: The unique utilities in OMEGAMON for Storage on z/OS, such as the Storage Toolkit and Dataset Attribute Database, log their messages to the Tivoli Enterprise Portal log. Consult the Tivoli Enterprise Portal log when you are troubleshooting these utilities.

Note: There is CPU and I/O overhead associated with detailed RAS1 tracing that might degrade performance of the monitoring agent. You must restore RAS1 tracing to the minimal KBB_RAS1=ERROR setting after problem diagnosis is completed.