DASD connected

Figure 2 shows two Tivoli Workload Scheduler for z/OS address spaces with a DASD 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 a submit/release DD name. The controller writes JCL, release commands, WTO messages, and cleanup requests into the submit/release data set. The tracker reads the submit/release data set 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 and writes the events into the event data set. An event-reader subtask started in the controller address space reads the event data set, and the current plan is updated.

Figure 2. A z/OS system connected through shared DASD

You can also configure this system without a submit/release data set. When the workstations destination is blank; batch jobs, started tasks, release commands, and WTO messages, are processed by the submit subtask automatically started in the controller address space. The event-tracking process remains unchanged.

Table 4 shows the initialization statements you can use to create the configuration in Figure 2.

OPCOPTS  OPCHOST(YES)
         ERDRTASK(1)
         ERDRPARM(STDERDR)
ROUTOPTS DASD(EQQSYSA)

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

ERDROPTS ERSEQNO(01)

EWTROPTS SUREL(YES)