Step 10. Creating JCL procedures for address spaces
Perform this task for a tracker, Data Store, controller, or standby controller.
You must define a JCL procedure or batch job for each Tivoli Workload Scheduler for z/OS address space.
See Defining subsystems for details.
The EQQJOBS dialog generates several members in the output library that you specified. The following table lists the members that provide samples for the scheduler’s address spaces:
| Address Space for: | Member |
|---|---|
| Controller and tracker | EQQCON (sample started task) EQQCONP (sample started task parameters) |
| Controller | EQQCONO (sample started task) EQQCONOP (sample started task parameters) |
| Tracker | EQQTRA (sample started task) EQQTRAP (sample started task parameters) |
| Server | EQQSER (sample started task) EQQSERP (sample started task parameters) |
| Data Store | EQQDST (sample started task) EQQDSTP (sample started task parameters) |
These members contain started task JCL that is tailored with the values you entered in the dialog. Tailor these members further, according to the data sets you require. Alternatively, you can copy a member from the SEQQSAMP library to one of your own libraries, and tailor it manually.
If you create a new library for your Tivoli Workload Scheduler for z/OS started-task procedures, remember to specify the library in the JES PROCLIB concatenation. Then you must restart JES to include the new library.
If you prefer, you can run Tivoli Workload Scheduler for z/OS as a batch job rather than as a started task. Here, the JCL can reside in any library and will require a job card, besides the JCL requirements in Table 29.