|
|
|
|
|
The example in Figure 105 demonstrates how Control-O accesses a list of prerequisite conditions (stored in the IOA Conditions file) to indicate the status of various components, such as jobs, or started tasks, in the working environment.
Figure 105 Example of Tracking CICS Region Statuses Using Prerequisite Conditions
ON MESSAGE = DFH1500
JNAME CICS* JTYPE J SMFID SYSTEM
ROUTE DESC CONSOLEID CONSOLE
APPEARED TIMES IN MINUTES And/Or/Not A
ON STRING = CONTROL IS BEING GIVEN TO CICS COL 022 - 051
JNAME CICS* JTYPE SMFID SYSTEM
ROUTE DESC CONSOLEID CONSOLE
APPEARED TIMES IN MINUTES And/Or/Not
OWNER IOAADMIN GROUP MODE PROD RUNTSEC
THRESHOLD
DESCRIPTION KEEP TRACK OF CICS REGIONS STATUSES VIA AN IOA CONDITION
===========================================================================
DO COND = CTO-%%$JOBNAME-UP STAT +
Explanation
When the DFH1500 message is detected and contains the string specified in the ON STRING statement (CONTROL IS BEING GIVEN TO CICS), this rule is triggered.
The JNAME field is used to specify the name of the job or started task that issued the message. In this case the value specified in the JNAME fields in both ON statements (CICS*) indicates that the rule is triggered whenever the specified message is issued from a CICS job or started task (region).
The DO COND statement is used to set a condition indicating whether or not the CICS region is up. The %%$JOBNAME system variable resolves to the name of the CICS region that issued the message. If, for example, the CICS region name is CICSTEST, the condition set in the DO COND statement is as follows:
DO COND=CTO-CICSTEST-UP STAT +
As a result of this DO COND statement, the CTO-CICSTEST-UP condition is added to the IOA Conditions file.
Using this rule (and other rules that remove conditions that are no longer true) Control-O can track the status of different CICS regions, and IOA components (such as Control-O rules and Control-M jobs) can be activated based on whether a specific region is up or down.
Parent Topic |