Code Matching for Event-Triggering Messages
INGMON allows you to pass up to three codes that, when specified, are used to determine a specific set of commands to be issued in case of an event-triggering message.
For message ING150I, SA z/OS creates an automation table entry where Code 1 is used to select commands by event severity. For other messages, you can override the default automation table entry and pass the appropriate tokens in Code 1, Code 2, and Code 3, as you require.
- selection
- Execute commands with the given selection or commands for which no selection is specified.
- #
- Perform pass processing and execute all commands that match the current pass.
- #selection
- Interpret selection as another pseudo message ID. Perform
pass processing for this message and execute all commands that match
the current pass.
This is useful for pass processing on behalf of the event triggering message, for example, ING150I. Suppose you have one entry for WARNING and one for CRITICAL. When you do pass processing for ING150I your pass counter may be on 5, for example, when the first CRITICAL event comes in (because you already had 4 WARNING events).
However, with #selection you can specify, for example, a value returned of #MYWARN WARNING and #MYCRIT CRITICAL for the corresponding levels. INGMON performs pass processing for the pseudo-message MYWARN and set the health status WARNING for a WARNING event. For a CRITICAL event it performs independent pass processing for the pseudo-message MYCRIT and finally sets a health status of CRITICAL.
Remember to set the IGNORE action for the pseudo-messages to avoid AT entries being built.