A PLEX configuration

Figure 30 shows four systems running in a sysplex environment, connected using cross-system coupling facility (XCF) communication links.

One controller and one tracker are started on each tracker image of the sysplex; one controller becomes the active one, while the others start as standby controllers. One server is started on the z/OS® image where the active controller runs, to handle requests from dialogs and PIF applications.

The &SYSCLONE system variable is assumed to be set to KA, KB, KB, and KC on systems A, B, C, and D respectively.

Figure 30. A Tivoli Workload Scheduler for z/OS PLEX environment
The graphic shows a Tivoli Workload Scheduler for z/OS PLEX environment.

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

Table 53. Example EQQPARM Members for the previous figure
EQQPARM members, shared among z/OS images

CONTROLR 

OPCOPTS  OPCHOST(PLEX)
         ERDRTASK(0)
         SERVERS(OSRV)
ROUTOPTS XCF(TRKA,TRKB,
             TRKC,TRKD)
XCFOPTS  GROUP(OPCGRP)
         MEMBER(CONTR)

SERVER 

SERVOPTS SUBSYS(OPCC)
         SCHEDULER(OSRV)

TRACKER 

OPCOPTS OPCHOST(NO)
        ERDRTASK(0)
        EWTRTASK(YES)
        EWTRPARM(TRKBEW)
XCFOPTS GROUP(OPCGRP)
        MEMBER(TR&SYSCLONE.)
TRROPTS HOSTCON(XCF)

TRKEW 

EWTROPTS EWSEQNO(1)