Using the INGOMX Programming Interface

INGOMX acts as the interface between operators (or auto-operators) and OMEGAMON. This includes not only any of the classic OMEGAMON monitors for CICS®, DB2®, IMS, and MVS, but also OMEGAMON XE monitors and other IBM Monitoring products running on z/OS.

For the classic OMEGAMON monitors, INGOMX can be used to issue OMEGAMON major, minor, and immediate commands, and to filter one or more exceptions of interest from the list of exceptions reported by OMEGAMON exception analysis. Each request is written to the console (but not exposed to NetView) in the format as produced by the OMEGAMON monitor. When exception filtering is requested, multiple exception lines for one exception are combined into a single line and written to the console as a single message if the filter criterion (XTYPE) matches. INGOMX is best used within a NetView PIPE.

The INGOMX SOAP interface allows you to issue any of the SOAP services supported by the TEMS SOAP server, for example to

• Obtain attributes of interest from a particular OMEGAMON XE object, for example, Job_name and CPU_percent from the OMEGAMON XE for z/OS object Address_Space_CPU_Utilization
• Start and stop situations as well as TEP workflow policies
• Issue a universal message
• Send an event into the IBM Monitoring platform

The full set of SOAP services and a description of the XML-syntax is described in IBM Monitoring Administrator's Guide.

The following examples illustrate the use of INGOMX. They are based on an OMEGAMON for MVS session with the name OMSY4MVS. The same techniques also apply to other OMEGAMON monitors. For more details, refer to IBM Z® System Automation Programmer's Reference.