XCF connected

Figure 5 shows two Tivoli Workload Scheduler for z/OS address spaces with an XCF connection in a z/OS monoplex.

You represent this system to Tivoli Workload Scheduler for z/OS by defining a computer workstation with a destination field that specifies the XCF member name of the tracker. The controller uses XCF services to transport JCL, release commands, WTO messages, and cleanup requests to members in the sysplex. The tracker receives data from XCF 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, transports the records to the controller across the XCF link, and writes the events into the event data set. The data router subtask in the controller receives the event records from XCF, and the current plan is updated.

Figure 5. A z/OS system with an XCF connection

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

OPCOPTS  OPCHOST(YES)
         ERDRTASK(0)
ROUTOPTS XCF(OPCTRK)
XCFOPTS  MEMBER(OPCCNT)
         GROUP(PLEXSYSA)

OPCOPTS OPCHOST(NO)
        ERDRTASK(0)
        EWTRTASK(YES)
        EWTRPARM(STDEWTR)
TRROPTS HOSTCON(XCF)
XCFOPTS MEMBER(OPCTRK)
        GROUP(PLEXSYSA)

EWTROPTS EWSEQNO(01)