Multi-access spool systems connected through shared DASD

Two z/OS JES2 MAS complexes connected through shared DASD shows two z/OS JES2 multi-access spool (MAS) complexes that are connected through shared DASD.

Systems A and B form a MAS complex. System A is the HCL Workload Automation for Z controlling system. It shares spool with System B, which is a controlled HCL Workload Automation for Z system. Work is sent directly to this complex by the controller on System A. The work is processed on one of these two systems, depending on installation parameters. You represent this complex to HCL Workload Automation for Z by defining a computer workstation with a blank destination field. That is, all work for this workstation is submitted to the system that the controller is started on.

Figure 1. Two z/OS JES2 MAS complexes connected through shared DASD

The graphic shows two z/OS JES2 MAS complexes connected via shared DASD.

Systems C and D, which are both HCL Workload Automation for Z controlled systems, form a second MAS complex. Work is sent to this complex via a submit/release data set. The destination field in the workstation description that represents this complex contains the DD name of the submit/release data set. The tracker on System C reads this data set and passes any new work to the complex for processing.

A tracker is installed on each system in the configuration. The event writer subtask of the tracker on each system writes events to an event data set on that system. Four event-reader subtasks, one for each of the event data sets, are started in the controller on System A. The controller reads the event data sets and updates the current plan.

When the controller is started on system A, it attempts to open the submit/release data set. If an I/O error occurs, the status of the workstation that represents the controlled MAS complex is set to offline. HCL Workload Automation for Z can then take automatic-workload-restart actions for operations at this workstation. These actions depend on the values that you specified on the WSOFFLINE keyword of the JTOPTS initialization statement.

Example EQQPARM members for the previous figure shows the initialization statements you can use to create the configuration in Two z/OS JES2 MAS complexes connected through shared DASD. This example assumes that some of the planned HCL Workload Automation for Z work on System C is submitted by a non-HCL Workload Automation for Z process. To control this work, the hold/release function is used. HOLDJOB(USER) is specified on the EWTROPTS statement for the tracker on System C. The RELDDNAME keyword is specified on the ERDROPTS statement of the event reader that reads event data set C. This keyword identifies the DD name of the submit/release data set that the controller should write release commands to.

Table 1. Example EQQPARM members for the previous figure

 EQQPARM members for System A
CONTROLR 
OPCOPTS    OPCHOST(YES)
           ERDRTASK4(4)
           ERDRPARM(ERDRA,ERDRB)
           ERDRC,ERDRD
ROUTOPTS   DASD(SUDSC)
 TRACKERA 
OPCOPTS    OPCHOST(NO)
           ERDRTASK(0)
           EWTRTASK(YES)
           EWTRPARM(TRKAEW)
TRROPTS    HOSTCON(DASD)

ERDRA 
ERDROPTS   ERSEQNO(1)

TRKAEW 
EWTROPTS

ERDRB 
ERDROPTS   ERSEQNO(2)

ERDRC 
ERDROPTS   ERSEQNO(3)
           RELDDNAME(SUDSC)

ERDRD 
ERDROPTS   ERSEQNO(4)

EQQPARM members for System B
TRACKERB 
OPCOPTS    OPCHOST(NO)
           ERDRTASK(0)
           EWTRTASK(YES)
           EWTRPARM(TRKBEW)
TRROPTS    HOSTCON(DASD)
 TRKBEW 
EWTROPTS

EQQPARM members for System C
TRACKERC 
OPCOPTS    OPCHOST(NO)
           ERDRTASK(0)
           EWTRTASK(YES)
           EWTRPARM(TRKCEW)
TRROPTS    HOSTCON(DASD)
 TRKCEW 
EWTROPTS   SUREL(YES
           HOLDJOB(USER)

EQQPARM members for System D
TRACKERD 
OPCOPTS    OPCHOST(NO)
           ERDRTASK(0)
           EWTRTASK(YES)
           EWTRPARM(TRKDEW)
TRROPTS    HOSTCON(DASD)
 TRKDEW 
EWTROPTS
Note: In this example, SUDSC is used for the user-defined DD name of the submit/release data set. This DD name appears in the started-task JCL of the controller, and in the destination field of the workstation that represents the controlled MAS system.