Determining if a specific OMEGAMON Monitoring Agent on z/OS caused a problem

In any problem scenario, gather all documentation at the time of the error. What appears to be a client problem might be a server problem, especially in the scenario where data is not showing up at the client. Use the following guidelines to collect the correct documentation for any problems.

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.