|
|
|
|
|
The example in Figure 100 demonstrates how Control-O can be used to notify appropriate individuals that a specific type of problem was detected.
Figure 100 Example of Notifying the System Programmer of a Problem
ON MESSAGE = IEE365I
JNAME JTYPE SMFID SYSTEM
ROUTE DESC CONSOLEID CONSOLE
APPEARED TIMES IN MINUTES And/Or/Not
OWNER IOAADMIN GROUP MODE PROD RUNTSEC
THRESHOLD
DESCRIPTION NOTIFYING THE SYSTEM PROGRAMMER OF A PROBLEM
DESCRIPTION SMF DATASET OR SYS1.PARMLIB COULD NOT BE OPENED
DESCRIPTION INFORM THE SYSPROG TSO USER AND CTO-PC
DESCRIPTION
===========================================================================
DO SHOUT = TO TSO-SYSPROG URGENCY R SYSTEM CTO282I
MESSAGE %%$MSG
DO CTOPCMSG = PAGE %%$MSG
Explanation
When the IEE365I message, which indicates that the SMF data set or SYS1.PARMLIB could not be opened, is detected, this rule is triggered:
DO SHOUT=TO TSO-SYSPROG
This statement sends a message to the specified destination. In this example the message that triggered the rule, indicated by the %%$MSG AutoEdit System variable, is forwarded to the system programmer.
TSO-SYSPROG can refer to one or more destinations, depending on the definition of this destination in the IOA Dynamic Destination Table. For more information, see the description of the IOA dynamic destination table in the IOA administration chapter of the INCONTROL for z/OS Administrator Guide.
DO CTOPCMSG=PAGE %%$MSG
The message that triggered this rule is also forwarded to Control-M/Links for Windows NT. Control-M/Links for Windows NT can then forward the message to the system programmer, for example, by using a paging device.
Parent Topic |