XCF connected

Figure 1 shows two IBM Z Workload Scheduler address spaces with an XCF connection in a z/OS monoplex.

You represent this system to IBM Z Workload Scheduler by defining a computer workstation with a destination field that specifies the XCF member name of the tracker. The Z 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 Z controller across the XCF link, and writes the events into the event data set. The data router subtask in the Z controller receives the event records from XCF, and the current plan is updated.

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

eqqi10cc The graphic shows a system with an XCF connection between the controller and tracker.

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

Table 1. Example EQQPARM members for Figure 5
Members for the Z controller Members for the tracker
OPCECNT
OPCOPTS  OPCHOST(YES)
         ERDRTASK(0)
ROUTOPTS XCF(OPCTRK)
XCFOPTS  MEMBER(OPCCNT)
         GROUP(PLEXSYSA)
TRKA
OPCOPTS OPCHOST(NO)
        ERDRTASK(0)
        EWTRTASK(YES)
        EWTRPARM(STDEWTR)
TRROPTS HOSTCON(XCF)
XCFOPTS MEMBER(OPCTRK)
        GROUP(PLEXSYSA)
 
 
STDEWTR
EWTROPTS EWSEQNO(01)
Note: In this example, the name of the monoplex is PLEXSYSA. The members in that group are:
OPCCNT
The controller
OPCTRK
The tracker
The tracker member name is defined in the destination field of the workstation.