Required data sets
Table 1 shows the data sets required by an IBM Workload Scheduler for z/OS started task. Include the data sets in your JCL procedures as indicated in this table.
| DD Name | Required by | Defines | |||
|---|---|---|---|---|---|
| Controller | Tracker | Server | Data Store | ||
| EQQADDS | ✓ | Application descriptions and JCL variable tables | |||
| EQQBRDS | ✓ | ✓ | A JES internal-reader | ||
| EQQCKPT | ✓ | Checkpoint data set | |||
| EQQCP1DS | ✓ | Primary current plan | |||
| EQQCP2DS | ✓ | Alternate current plan | |||
| EQQCXDS | ✓ | Current plan extension | |||
| EQQEVDS | ✓ | ✓ | Event data set for the submit checkpointing function and for the event-writer task | ||
| EQQEVLIB | ✓ | Configuration file repository for event-triggered resource handling | |||
| EQQJBLIB | ✓ | JCL PDS libraries | |||
| EQQLOGRC | ✓ | Joblog and Restart Information pending requests log data set | |||
| EQQJS1DS | ✓ | Primary JCL repository | |||
| EQQJS2DS | ✓ | Alternate JCL repository | |||
| EQQJTABL | ✓ | Job table log file. The scheduler considers this data set as required only if you defined at least one critical job. Allocate it with the same size as EQQJTARC. | |||
| EQQJTARC | ✓ | Job-tracking archive | |||
| EQQJTnn | ✓ | Job-tracking logs | |||
| EQQLTDS | ✓ | Long-term plan | |||
| EQQMLIB | ✓ | ✓ | ✓ | ✓ | Message library |
| EQQMLOG | ✓ | ✓ | ✓ | ✓ | Output message log |
| EQQNCPDS | ✓ | New current plan | |||
| EQQNCXDS | ✓ | New current plan extension | |||
| EQQNXDDS | ✓ | NCP extension | |||
| EQQOIDS | ✓ | Operator instructions | |||
| EQQPARM | ✓ | ✓ | ✓ | ✓ | Parameter library |
| EQQRDDS | ✓ | Special resource descriptions | |||
| EQQSCPDS | ✓ | Current plan backup copy data set for the creation of Symphony. Needed for integration with IBM® Tivoli® Monitoring. | |||
| EQQSIDS | ✓ | Side information; ETT criteria and configuration data | |||
| EQQWSDS | ✓ | Workstation, calendar and period descriptions | |||
| EQQXD1DS | ✓ | CP1 extension | |||
| EQQXD2DS | ✓ | CP2 extension | |||
Note:
- The data sets that are required for a controller are also required for a standby controller.
- The number of job-tracking-log data sets to include depends on the value that you specify in the JTLOGS keyword of the JTOPTS initialization statement. Specify at least 3 job-tracking logs. The default value is 5.
- You must specify EQQEVDS for a controller even if an event writer is not started in the controller address space. The EQQEVDS data set is used for submit checkpointing. It can be the same data set that is used by an event-writer function. Use a unique EQQEVDS for each address space.
- In order to set the TCP⁄IP task
up correctly, you need to change the scheduler start procedure to
include the C runtime libraries (CEE.SCEERUN in the STEPLIB DD statement).
If you have multiple TCP⁄IP stacks, or if the name you used for the procedure that started the TCPIP address space was not the default (TCPIP), then you must change the start procedure to include the SYSTCPD DD card to point to a data set containing the TCPIPJOBNAME parameter.
The standard method to determine the connecting TCP⁄IP image is:- Connect the TCP⁄IP specified by TCPIPJOBNAME in the active TCPIP.DATA
- Locate TCPIP.DATA using the SYSTCPD DD card.