Implementing support for started-task operations

The JCL procedures for started-task operations started by Tivoli Workload Scheduler for z/OS must be stored in a PDS concatenated on the EQQJBLIB DD name. You can include existing data sets, such as SYS1.PROCLIB, if you prefer. Preparation, tailoring, and variable substitution are handled the same way as for batch job operations. When a started-task operation is started by Tivoli Workload Scheduler for z/OS, the JCL procedure is written to the started-task-submit data set (EQQSTC) on the system where the operation is to be run. Tivoli Workload Scheduler for z/OS issues a START command for this procedure and then removes the JCL procedure from the EQQSTC data set.

JES2 users should specify the started-task-submit data set on the PROCnn DD statement of the JES2 JCL procedure on each z/OS system. The suffix nn is the value specified for the PROCLIB parameter of the STCCLASS statement in JES2PARM. To ensure that the correct version of the JCL procedure is started, place the EQQSTC data set first in the concatenation.

JES3 users should specify the started-task-submit data set on the IATPLBnn DD statement of the JES3 global system. The suffix nn is the value specified in the JES3 standards parameter STCPROC. To ensure that the correct JCL procedure will be started, place the EQQSTC data set first in the concatenation. For each submit task that is running on a JES3 local system in the JES3 complex, also include that data set in the JES3 global concatenation.

If you do not use the Restart and Cleanup function, you must follow the previous instructions to work with started-task operations. Otherwise, because the Restart and Cleanup function adds a job card to the procedures for scheduled STC workstation operations at the same time that it adds the //TIVDSTxx output JCL statements, there are some exceptions to the previous instructions if you want to use the Restart and Cleanup function. The JCL for a started task can contain a job card only if the JCL is in a data set in the IEFPDSI or IEFJOBS concatenations of MSTJCLxx when the start command is issued.

You must add the EQQSTC data set to the IEFPDSI DD statement in MSTJCLxx instead of to the JES2 PROCnn or the JES3 global IATPLBnn DD statement as mentioned above.

In addition, all data sets listed in IEFPDSI must be included in the system master catalog.

Notes:
  1. To include EQQSTC, you must restart JES.
  2. Do not use the BLDL parameter of the JES3 PROC statement to specify the procedure name of a started task that is to be scheduled by Tivoli Workload Scheduler for z/OS.

The EQQSTC data set can be shared by Tivoli Workload Scheduler for z/OS subsystems that run on the same z/OS® image. If you use global resource serialization (GRS), the EQQSTC data set can be shared by all z/OS systems defined in the GRS ring if you propagate requests for the resource. To propagate the resource requests to all systems in the ring, define the resource SYSZDRK.data data set name in the SYSTEM inclusion RNL of the GRSRNLnn member of SYS1.PARMLIB. For more information about defining the GRS resource name list, see z/OS Initialization and Tuning Reference.