Relationships and dependencies
Next, SA z/OS would now issue all of the start commands at the same time and the starts for VTAM® and TSO would fail. To avoid complications, specify the sequence in which the resources are started (and stopped).
About this task
SA z/OS uses relationships, which run from the dependent
resource to the supporting resource, to control the resource start and stop sequence. Each type of
relationship has a name and some can be complex. For this exercise, you are going to use one of the
simple ones here: HasParent.
TSO ---- HasParent --> VTAM
VTAM --- HasParent --> JES
In the Customization Dialog, you always define relationships from the point of view of the dependent resource, and specify the name of the supporting resource.
Procedure
-
You start by selecting the TSO application and selecting the
RELATIONSHIPS from its Policy Selection panel. The
Relationship Selection List panel is displayed.
COMMANDS ACTIONS VIEW HELP ------------------------------------------------------------------------------ Relationship Selection List Command ===> ________________________________________________________________ Entry Type : Application PolicyDB Name : TEST_PDB Entry Name : TSO Enterprise Name : TEST_SYSTEMS External Startup. . . ________ (INITIAL ALWAYS NEVER) External Shutdown . . ________ (FINAL ALWAYS NEVER) Action # Type Supporting Resource Auto Chain ******************************* Bottom of data ******************************* No entries currently exist. Use the NEW command to create an entry. -
Type new on the command line and press Enter to create a relationship.
The Define Relationship panel is displayed.
COMMANDS HELP ------------------------------------------------------------------------------ Define Relationship Command ===> ______________________________________________________________ Entry Type : Application PolicyDB Name : TEST_PDB Entry Name : TSO Enterprise Name : TEST_SYSTEMS Description. . . . . ________________________________________ Relationship Type. . _________________ MAKEAVAILABLE MAKEUNAVAILABLE PREPAVAILABLE PREPUNAVAILABLE HASPARENT HASPASSIVEPARENT HASMONITOR PEEROF FORCEDOWN EXTERNALLY Supporting Resource. __________________________________ Resource Name Sequence Number. . . ___ Sequence Number (1-99,blank) Automation . . . . . _________ ACTIVE PASSIVE Chaining . . . . . . _______ STRONG WEAK Condition . . . . . _______________________________________________ Satisfy condition (? for list of possible values) - Enter HASPARENT in the Relationship Type field and VTAM/APL/= in the Supporting Resource field. The specific notation for the supporting resource, with the equal sign (=) as a placeholder for the system name, means that the VTAM application is sharing the same system as the TSO application. If you linked the same pair of application definitions to three different systems, each copy of TSO would be dependent on the corresponding copy of VTAM.
-
Press PF3 to exit the panel. The Relationship Selection List panel is
updated with the new relationship defined.
COMMANDS ACTIONS VIEW HELP ------------------------------------------------------------------------------ Relationship Selection List Row 1 to 1 of 1 Command ===> _______________________________________________________ Entry Type : Application PolicyDB Name : TEST_PDB Entry Name : TSO Enterprise Name : TEST_SYSTEMS External Startup. . . _________ (INITIAL ALWAYS NEVER) External Shutdown . . _________ (FINAL ALWAYS NEVER) Action # Type Supporting Resource Auto Chain ______ __ HASPARENT VTAM/APL/= ******************************* Bottom of data ******************************* -
Repeat this process to create a
HasParentrelationship from VTAM to JES.