![Previous Topic: Evaluating Process Events](574.png)
![Next Topic: Process Events](573.png)
Using System State Manager › How to Specify and Store Actions › Search Order for Action Tables › Example of Action Selection
Example of Action Selection
This example shows the state mismatch action selection. Some columns were omitted for clarity.
NAME CURRENT_STATE DESIRED_STATE ACTMODE TYPE
RES1 DOWN UP STC
RES2 DOWN UP STC
RES3 DOWN UP BOUNCE STC
RES4 STARTING UP STC
Following is an example of the actions that were selected in response to the above state mismatch:
ACTION_PROCESS ACTION_CURRENT ACTION_DESIRED ACTION_MODE ACTION_RES_TYPE ACTION_TEXT
1 ACTION DOWN UP MVSCMD("START &JOBNAME")
2 ACTION DOWN UP RES2 MVSCMD("S DJOB,PARM='IPL'")
3 ACTION DOWN BOUNCE TSOCMD("OI BOUNCE")
4 ACTION DOWN UP BOUNCE TSOCMD("OI REBOUNCE")
5 ACTION STARTING UP SETCOL("CURRENT_STATE,DOWN")
In the previous example, the following actions are taken in response to the resource state change events:
- For RES1-Action 1 is selected with a score of 16. Action 5 is not considered for this resource because the current state does not match the ACTION_CURRENT column of the action table. Actions 2, 3, and 4 are bypassed because there are non-null columns in the action table that do not match the resource.
- For RES2-Action 2 is selected with a score of 18. Action 1 also matches the resource; however, its score is 16. Actions 3 and 4 are rejected because the ACTION_MODE column is non-null and it does not match the resource. Action 5 is not even considered because the current state does not match the value of the ACTION_CURRENT column of the action table.
- For RES3-Action 4 is selected with a score of 24. Actions 1 and 3 are also matches with scores of 16 and 8 respectively.
- For RES4-Action 5 is selected with a score of 16. No other actions are considered.
Copyright © 2014 CA.
All rights reserved.
![Previous Topic: Evaluating Process Events](574.png) ![Next Topic: Process Events](573.png)
|
|