SDF Tree Structure Definitions

Two tree structure definitions are required to set up the SDF hierarchy for systems SY1 and SY2.

Figure 1 shows the tree structure definition for both systems. This tree structure is defined in a NetView® DSIPARM data set member named SY1TREE.

Figure 1. SDF Example: Tree Structure Definition for SY1 and SY2

1 &SDFROOT.
 2 SYSTEM
  3 JES
  3 VTAM
  3 RMF
  3 TSO
  3 AOFAPPL
   4 AOFSSI
  3 APPLIC
   4 SUBSYS
 2 ACTION,GREEN
  3 WTOR,GREEN
 2 GATEWAY

SDF initialization uses the common global AOF_AAO_SDFROOT.n to generate as many tree structures as system names are found in the global for each structure that starts with 1 &SDFROOT..

Figure 2 shows the hierarchy of monitored resources defined by the SY1 tree structure.

Figure 2. SDF Example: Hierarchy Defined by SY1 Tree Structure. The diagram shows how the order of dependence relates to level number.

                                                           1 SY1
                                                              │
                                 ┌────────────────────────────┴───────────────┬──────────────┐
                                 │                                            │              │
                              2 SYSTEM                                     2 ACTION       2 GATEWAY
                                 │                                            │
   ┌───────────┬───────────┬─────┴─────┬───────────┬───────────┐              │
   │           │           │           │           │           │              │
3 JES       3 VTAM      3 RMF       3 TSO       3 AOFAPPL   3 APPLIC       3 WTOR
                                                   │           │
                                                   │           │
                                                4 AOFSSI    4 SUBSYS

This structure contains specific entries for the major system components, JES, RMF, VTAM, and TSO, as well as NetView (AOFAPPL) and the NetView SSI (AOFSSI). Note that the hierarchy differs from that defined in the SA z/OS automation control file. This is because the operator's view of these subsystems differs from the logical sequence that they are managed in by SA z/OS for startup and shutdown purposes.

The SYSTEM, APPLIC, and ACTION entries are logical, and may be used to view the status of all entries below them in priority order.

The SUBSYS, WTOR, and GATEWAY entries are also logical, and may be used to display the status of SUBSYSTEM, WTOR, and GATEWAY resource types. The status of any subsystem not appearing elsewhere in the tree will be queued under the SUBSYS entry. Similarly, WTORs and gateway status will be queued under WTOR and GATEWAY respectively.

A similar tree structure must be provided for SY2. As both systems are running the same set of base software, the tree structures are identical, except for the root (level 1) name, which will be SY2 rather than SY1. The member holding the tree structure must be defined in the Netview DSIPARM data set on each system. The tree structure is referenced by %INCLUDE statements in the base SDF tree definition member, AOFTREE, as follows:

%INCLUDE(SYXTREE)

Because SY1 is the focal point system in this example, the global AOF_AAO_SDFROOT.n on system SY1 must define both systems, SY1 and SY2.

Because our example does not require SY2 to function as a backup focal point system, the global AOF_AAO_SDFROOT.n system SY2 does not need to be specified.