Determining whether the problem was caused by an OMEGAMON XE Monitoring Agent on z/OS
This section describes how to identify problems caused by a specific OMEGAMON® XE Monitoring Agent. Sometimes it is difficult to trace the origin of a problem. For example, a problem might first be displayed in a Tivoli® Enterprise Portal client, but the client is reflecting a more basic problem with the Tivoli Enterprise Monitoring Server.
In any problem scenario, all documentation should be gathered at the time of the error. What appears to be a client problem could very well be a server problem, especially in the scenario where data is not showing up at the client. The following guidelines are for collecting the correct documentation for any problems reported.
As you collect logs, create an exact description of the problem. For reproducible problems, document the exact navigation path that produced the error. Screen prints might also help in the problem determination.
In your problem report, try to use the correct terminology when describing the problem (for example, workspaces, views, navigators, events, and links). Consistent use of the terminology helps IBM® Software Support to understand the problem quickly.
The sections that follow discuss types of problems that you might see and how to capture information needed to diagnose those problems.