VTAM connected

Figure 3 shows two Tivoli Workload Scheduler for z/OS address spaces with a VTAM® connection on a z/OS system.

You represent this system to Tivoli Workload Scheduler for z/OS by defining a computer workstation with a destination field that specifies the LU name of the tracker. The controller transmits JCL, release commands, WTO messages, and cleanup requests across the LU-LU link using the NCF component. The tracker receives data across the VTAM link and performs the following actions:

Submits JCL for batch jobs to the JES internal reader
Writes the JCL for started tasks into the EQQSTC data set and issues START procname z/OS commands
Issues JES release commands for jobs in HOLD status
Submits the cleanup job.

The event-tracking routines create event records to describe activities that occur on the system. These records are added to the tracker event writer queue in ECSA. The tracker processes the queue, transmits the records to the controller across the VTAM link, and writes the events into the event data set. The VTAM subtask in the controller receives the event records, and the current plan is updated.

Note:

You must specify EQQEVDS for a controller, even if an event writer is not started in the controller address space. The EQQEVDS data set is used for submit checkpointing. It can be the same data set that is used by an event-writer function. Use a unique EQQEVDS for each address space of the scheduler.

Figure 3. A z/OS system with a VTAM connection

The graphic shows a system with a VTAM link between the controller and tracker.

Table 5 shows the initialization statements you can use to create the configuration in Figure 3.

Table 5. Example EQQPARM members for Figure 3

Members for the controller	Members for the tracker
OPCECNT OPCOPTS OPCHOST(YES) ERDRTASK(0) NCFTASK(YES) NCFAPPL(CNTSYS) ROUTOPTS SNA(TRKSYS)	TRKA OPCOPTS OPCHOST(NO) ERDRTASK(0) EWTRTASK(YES) EWTRPARM(STDEWTR) NCFTASK(YES) NCFAPPL(TRKSYS) TRROPTS HOSTCON(SNA) SNAHOST(CNTSYS)

	STDEWTR EWTROPTS EWSEQNO(01)
Note: In this example, the LU name of the controller is CNTSYS and the tracker uses TRKSYS. The tracker LU is defined in the destination field of the workstation.