Implementing the Solution

Procedure

  1. On the Customization Dialog Primary Menu panel, open the policy database that you created in the scenario described in How to Work with Resources.
  2. Create a new application group called AOR_MOVE with these values:
    • Application Group Type: SYSPLEX
    • Nature: MOVE
    • Automation Name: AOR_MOVE
  3. Use the WHERE USED policy item to link the application group AOR_MOVE to SYSPLEX1.

    SA z/OS generates the APG resource: AOR_MOVE/APG

  4. Link application CICS1AR1 to application group AOR_MOVE.
    SA z/OS generates the following APL resources:
    CICS1AR1/APL/SYSTEM1
    CICS1AR1/APL/SYSTEM2
    CICS1AR1/APL/SYSTEM3
  5. In application group AOR_MOVE, select policy item RESOURCES and set the following preferences for the new APL resources:
    • 900 for CICS1AR1/APL/SYSTEM1, so that starting AOR_MOVE/APG starts CICS1AR1/APL/SYSTEM1
    • 600 for CICS1AR1/APL/SYSTEM2, so that it starts if CICS1AR1/APL/SYSTEM1 fails
    • 500 for CICS1AR1/APL/SYSTEM3, so that it starts if CICS1AR1/APL/SYSTEM2 also fails
  6. Create a new application group called TOR_GRP with these values:
    • Application Group Type: SYSTEM
    • Nature: BASIC
    • Automation Name: TOR_GRP
  7. Use the WHERE USED policy item to link the application group TOR_GRP to system SYSTEM3.

    SA z/OS generates the APG resource: TOR_GRP/APG/SYSTEM3

  8. Link application CICS1TOR to application group TOR_GRP. SA z/OS generates the APL resource: CICS1TOR/APL/SYSTEM3
  9. Define a HASPARENT relationship between CICS1TOR/APL/SYSTEM3 as the child (dependent resource) and AOR_MOVE/APG as the parent (supporting resource) as follows:
    1. For application CICS1TOR, select policy item RELATIONSHIPS.
    2. On the Relationship Selection List panel, enter new hasparent at the command line.
    3. On the Define Relationship panel, enter resource AOR_MOVE/APG in the Supporting Resource field.
  10. Create a new application group called CICS_APL with these values:
    • Application Group Type: SYSPLEX
    • Nature: BASIC
    • Automation Name: CICS_APL
  11. Use the WHERE USED policy item to link application group CICS_APL to group SYSPLEX1.
    SA z/OS generates the APG resource: CICS_APL/APG
  12. Make TOR_GRP/APG/SYSTEM3 and AOR_MOVE/APG members of CICS_APL/APG as follows:
    1. In application group CICS_APL, select policy item RESOURCES.
    2. Overtype NO in the Show all Resources field with YES and press Enter.

      This displays the resources that have been generated so far.

    3. Use action s to select the following resources:
      • AOR_MOVE/APG
      • TOR_GRP/APG/SYSTEM3
  13. Create a new event called BCKUPFIN.

    This event is set whenever the backup process that is required is completed.

    Note: SA z/OS can automatically set this event by trapping message IEF404I from the backup process. Use the INGEVENT command to set events.
  14. Select policy item CONDITION and, on the Unset Condition panel that appears, enter the option that suits your needs in the Unset Condition field, for example UP.
    Background:
    • The condition for unsetting an event will be checked on the observed status. There are eleven possible values for the observed status: six that indicate availability and five that indicate unavailability (see Observed Status in IBM Z System Automation User's Guide for details). Among those values that indicate availability, there is one named STARTING. The UP condition, for example, means: the observed status has a value that indicates availability, but is not the value STARTING.
    • The observed status belongs to generated resources, not to policy objects. In other words: a policy object does not have an observed status. Only the resources that are generated from the policy object have an observed status. So there is an observed status for each of the boxes in Figure 2, but not for the boxes in Figure 1.
    • As a result of all this, the condition for unsetting an event only has an effect when the event is related to a generated resource because only then is there an observed status that the condition can be checked on.
    • The only way that an event can be related to generated resources is via a trigger, as follows: when the event is linked to a trigger and the trigger is linked to an APL, APG, or MTR policy object, the event will be indirectly related to every resource that is generated from that APL, APG, or MTR policy object.
    • The key to understanding the effect of the unset condition is that SA z/OS maintains a separate event value for each generated resource that an event is indirectly related to. So an event may be set for one generated resource, but unset for another at the same time.
    • The effect of UP, for example, is that the event will be unset for a particular generated resource as soon as the observed status of that particular generated resource is given a value that indicates availability, but is different from the value STARTING.

  15. Create a new trigger called CHCKBCKP, then enter trigger details as follows to make the trigger check backup completion before startups:
    1. On the Policy Selection panel for the new trigger, select policy item CONDITION.
    2. On the Trigger Conditions panel, select condition STARTUP 1.
    3. On the STARTUP Condition for Trigger panel that follows, use action s to change the status of event BCKUPFIN to SELECTED.
  16. Link trigger CHCKBCKP to application CICS1AR1 as follows:
    1. Select policy item WHERE USED for trigger CHCKBCKP.
    2. On the Where Used panel, select the application CICS1AR1.

    As a result of linking trigger CHCKBCKP to both application CICS1AR1 and event BCKUPFIN, SA z/OS maintains a separate BCKUPFIN value for each of the three resources that were generated from application CICS1AR1 (that is, CICS1AR1/APL/SYSTEM1, CICS1AR1/APL/SYSTEM2, and CICS1AR1/APL/SYSTEM3).When you use INGEVENT to set the event, you can supply the name of one of these resources so that the event is only set for that particular resource, but remains unset for the others. If you do not supply a resource parameter with INGEVENT, the event will be set for all three resources. They will, however, still be independent of each other, so they might be unset at different times.

  17. Create a service period called CICS_SVP, then enter schedule details as follows:
    1. On the Policy Selection panel for the new service period, select policy item SERVICE WINDOW.
    2. On the Service Windows panel, scroll down to SATURDAY and WEEKDAY and fill in the following values:
      Saturday U    08:00 14:00                                                    
               D                                                                   
       Weekday U    07:00 18:00                                                    
               D                                                                   
  18. Link service period CICS_SVP to application group CICS_APL as follows:
    1. For service period CICS_SVP, select policy item WHERE USED.
    2. On the Where Used panel, select the application group CICS_APL.