Optional data sets

IBM Z Workload Scheduler optional data sets shows the data sets that you can optionally include in your JCL procedures. Specify these data sets only if you want to use the function with which they are associated.

Table 1. IBM Z Workload Scheduler optional data sets
DD Name Can be used by Defines
Controller Tracker Server Data Store Output collector
AUDITPRT ✓ Input to EQQAUDIT
EQQDLnn ✓ Dual job-tracking logs
EQQDUMP ✓ ✓ ✓ Diagnostic dump output
EQQEVDnn ✓ Event data set for an event-reader task
EQQINCWK ✓ JCC incident work file
EQQJCLIB ✓ JCC library for message tables and for data set triggering selection table
EQQMONDS ✓ Data set used by monitoring task to store events for IBM® Tivoli® Monitoring.
EQQOUCEV ✓ ✓ Data set used for the communication that takes place between the controller and Output collector in the retrieval process of the job logs produced in the z-centric environment.
EQQOUCKP ✓ ✓ Data set used for the communication that takes place between the controller and Output collector in the retrieval process of the job logs produced in the z-centric environment.
EQQPKIxx ✓ Primary index
EQQPRLIB ✓ ✓ Automatic-recovery procedures
EQQSCLIB ✓ Script library
EQQSDFnn ✓ Structured data files
EQQSKIxx ✓ Secondary index
EQQSTC ✓ ✓ Started-task-submit data set
EQQSUDS ✓ Submit/release data set for an event-writer task
EQQTROUT ✓ Input to EQQAUDIT
EQQTWSCS ✓ ✓ Data set for centralized script support in end-to-end scheduling with fault tolerance capabilities
EQQTWSIN ✓ ✓ Input event data set in end-to-end scheduling with fault tolerance capabilities
EQQTWSOU ✓ ✓ Output event data set in end-to-end scheduling with fault tolerance capabilities
EQQUDFnn ✓ Unstructured data files
STDENV ✓ This data set/member contains the environment variables of the end-to-end with fault tolerance capabilities processes
STEPLIB ✓ ✓ ✓ Load-module library
SYSMDUMP ✓ ✓ ✓ Dump data set
user-defined ✓     Submit/release data set for the controller submit task
Note:
  1. The optional data sets that you specify for a controller must also be specified for a standby controller.
  2. If you use dual job-tracking, the number of dual job-tracking logs (EQQDLnn) must be the same as the number of job-tracking logs (EQQJTnn).
  3. Include EQQDUMP and SYSMDUMP for diagnostic purposes.
  4. The EQQEVDnn DD name identifies the event data set for an event-reader task. The nn value is the sequence number specified in the ERSEQNO keyword of the event reader (controller only) that will process this data set. It is always a 2-digit number. That is, if the sequence number is less than 10, a leading 0 must be added.
  5. Specify the EQQSTC data set if you use IBM Z Workload Scheduler to schedule started-task operations.
  6. Use the standard JCL naming conventions for each user-defined DD name; that is, 1-8 alphanumeric or national characters, of which the first character must be alphabetic or national.
  7. The submit/release data set is identified by a controller, with a user-defined DD name. The same name must appear in the procedure JCL, the DASD keyword of the ROUTOPTS statement, and the destination field of the workstation representing the system that work is to be sent to. The same data set is identified in a tracker, by the EQQSUDS DD name.
  8. When using end-to-end functions, the same EQQTWSIN, EQQTWSOU, and EQQTWSCS data sets must be allocated to the controller and the end-to-end server.
  9. The STDENV DD name can point to a sequential DS or a PDS member (for example, a member of the PARMLIB) in which the user can define environment variables to initialize Language Environment®. STDENV must have a F or FB format with a record length equal or greater than 80. In this data set/member you can put your environment variables specifying VARNAME=value. On each row you can specify only 1 variable, characters after column 71 are ignored. If you need more than 71 characters, you can add any character in column 72 and continue on the next row (the character in column 72 is ignored).
  10. THE EQQTROUT DD card must point to a data set or be dummy, but it cannot be removed from the daily plan JCL. In particular if a CP extend or replan job is submitted with the EQQTROUT DD deleted or commented out, the DRTOP/DNTOP JOBSTEP can end with RC08, even if a new plan is created and taken over, because EQQTROUT could not be opened. Also the data set pointed by the EQQTROUT DD must be allocated by using the DCB values provided in the allocation JCL sample: RECFM=VB,LRECL=32756,BLKSIZE=32760 otherwise the contents of the data set will be unreadable.

    For detailed information about configuring the environment variables for SSL protocol, see how to enable the FIPS compliance over the SSL secured connection in Scheduling End-to-end with Fault Tolerance Capabilities.

  11. Data sets EQQOUCEV and EQQOUCKP are required if you activate the Output collector started task.