Overview

The SA z/OS OMEGAMON interface lets you gather a wide range of performance data on a system. You can gather data from the following performance monitoring products:

  • IBM OMEGAMON for z/OS
  • IBM OMEGAMON for CICS on z/OS
  • IBM OMEGAMON for IMS on z/OS
  • IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS
  • Other IBM Tivoli Monitoring products running on z/OS

Exception analysis is an OMEGAMON classic feature that monitors predefined thresholds in a system. Each time exception analysis is invoked, an exception is displayed on the OMEGAMON console if a threshold is exceeded. Using SA z/OS, you can then act on these exception alerts by running execs or issuing commands, including issuing commands back to the host OMEGAMON.

Situations are much like exceptions but they are based on a combination of logical expressions and even on the status of other embedded situations. Each product based on the IBM Monitoring infrastructure, such as IBM® OMEGAMON, provides a set of predefined situations that you can use as is, or modify as you wish. You can also create your own situations to tailor the monitoring to your specific needs. Situations are edited and displayed on the Tivoli Enterprise Portal (TEP). Using a TEP function called Reflex Automation, you can inform SA z/OS about a particular situation and then act upon it.

IBM Monitoring services also allow you to interact with each and every product based on this infrastructure through a standardized SOAP services interface on the Tivoli Enterprise Monitoring Server (TEMS). SOAP services exist, for example, to obtain data from a particular object collected by IBM OMEGAMON for z/OS (formerly IBM Tivoli OMEGAMON XE on z/OS). Other services allow you to automatically manage situations and TEP workflow policies, or to send universal messages to the universal message console.

You can set up monitor resources to:

  • Monitor sets of exceptions that may be of interest using an active monitor resource and set an application's health status based on the existence of such exceptions
  • React to and resolve conditions that cause those exceptions
  • Monitor sets of situations that may be of interest using a passive monitor resource, set an application's health status and react to and resolve conditions that cause those situations