Using the INGMTRAP Monitor Command

INGMTRAP is a customized interface to INGOMX that provides filtering capabilities for exceptions of interest as reported by OMEGAMON exception analysis and triggering of automation on behalf of such exceptions. For each exception that matches the XTYPE filter that is provided by the caller, INGMTRAP issues message ING080I, which is exposed to NetView.

For example:

ING080I CI2XREP/MTR/KEYA OMSY4MVS OMIIMVS XREP Number of Outstanding Replies = 4

If no exception matches the XTYPE filter that is provided by the caller, INGMTRAP creates a ING081I message that is not exposed to NetView but written to the monitor resource's log to document that no exception has been found. For example:

ING081I CI2XREP/MTR/KEYA OMSY4MVS OMIIMVS NO EXCEPTION FOUND

INGMTRAP can only be used as a monitor command. This means that it has to be specified directly as a monitor command in the definition of a monitor resource, or it has to be called on behalf of such a monitor command. The following example illustrates what you need to specify on the MONITOR INFO policy in entry type monitor resource (MTR) in order to trap outstanding operator replies that are reported by OMEGAMON for MVS session OMSY4MVS:

INGMTRAP NAME=OMSY4MVS,XTYPE=(XREP)

Be careful when specifying a list of exceptions: each exception may cause an ING080I message to be issued. Because each occurrence of an ING080I message triggers health status processing of the monitor resource, make sure you understand the impact that this may have on the monitor resource's final health status.

For more details about INGMTRAP refer to IBM Z® System Automation Programmer's Reference. For more details about defining monitor resources, refer to IBM Z System Automation Defining Automation Policy .