Controlling a z/OS system through a VTAM link

Figure 31 shows a z/OS system connected to the Tivoli Workload Scheduler for z/OS host via a VTAM® link.

You represent each system by a computer workstation. The destination field in the workstation description for System A is left blank. Work for this workstation is started on System A. The destination field for the System B workstation contains the VTAM application ID of the tracker at this node. Work is transmitted from the host to the tracker and is then initiated on System B.

Figure 31. Controlling a z/OS system through a VTAM link

On System A, an event writer writes events to event data set A, which is read by an event reader subtask at the controller. On system B the tracker event-writer subtask is started with a reader function, EWSEQNO is defined in the EWTROPTS statement. This means that the event writer passes the events to NCF for transfer to the controller at the same time as they are written to the event data set.

Automatic workload restart can be used in this configuration if the controller cannot communicate with the tracker on system B. The status of the workstation for System B is set to offline if z/OS is stopped or fails, if the tracker is stopped or fails, or if the VTAM link is lost. WLR actions are taken according to the WSOFFLINE keyword of the JTOPTS initialization statement.

Table 54 shows the initialization statements you can use to create the configuration in Figure 31.

OPCOPTS  OPCHOST(YES)
         ERDRTASK(1)
         ERDRPARM(ERDR1)
         NCFTASK(YES)
         NCFAPPL(NCFAPPL1)
ROUTOPTS SNA(NCFAPPL2)

OPCOPTS OPCHOST(NO)
        ERDRTASK(0)
        EWTRTASK(YES)
        EWTRPARM(TRKAEW)
TRROPTS HOSTCON(DASD)

ERDROPTS ERSEQNO(1)

EWTROPTS

OPCOPTS OPCHOST(NO)
        ERDRTASK(0)
        EWTRTASK(YES)
        EWTRPARM(TRKBEW)
        NCFTASK(YES)
        NCFAPPL(NCFAPPL2)
TRROPTS HOSTCON(SNA)
        SNAHOST(NCFAPPL1)

EWTROPTS EWSEQNO(1)