Generating batch-job skeletons
To ensure that all files are correctly allocated, you must generate the batch-job skeletons before creating the sample job JCL.
Several controller functions, such as daily planning, are performed by batch jobs that are submitted from the Tivoli Workload Scheduler for z/OS dialog. To generate the skeleton JCL for these jobs:
- Select option 2 from the EQQJOBS main menu. This panel is displayed:
Figure 17. EQQJOBS1 - Generate Tivoli Workload Scheduler for z/OS batch-job skeletons
EQQJOBS1 ------------ GENERATE TWSz BATCH-JOB SKELETONS -------------------- Command ===> Enter the name of the output library. This should be a fully qualified data set name without any enclosing apostrophes. This library should be allocated to ISPSLIB. Batch-job skeletons ===> CCOPC.OPCA.JCLSKELS_____________________________ The following data set names are used by one or more of the generated job You can specify an asterisk (*) to indicate the name of the subsystem. Message library name ===> OPC.SEQQMSG0____________________________________ Parameter library ===> CCOPC.*.PARM____________________________________ Member in parameter library ===> BATCHOPT Checkpoint data set ===> CCOPC.*.CKPT____________________________________ Press ENTER to continue
- Batch-job skeletons
- Required input. Enter the name of the library where the JCL
skeletons are to be stored. Before you use the Tivoli Workload Scheduler for z/OS dialog to
submit batch jobs, allocate this library to the ISPSLIB DD statement
in the TSO session of dialog users.
Step 13. Setting up the ISPF environment explains how you set up the dialog. You can create a new library for the skeleton JCL members or put them in an existing skeleton-JCL library.
In the following fields, you can enter &XOPCNM. as one of the qualifiers for the data set names. This is an ISPF variable that is stored in the profile and is the same variable that you specify in option 0.1 (SUBSYSTEM NAME) in the Tivoli Workload Scheduler for z/OS dialogs. When a skeleton is then used by a dialog of the scheduler, &XOPCNM. is substituted with the name of the scheduler subsystem that is being used.
Ensure that &XOPCNM. ends with a period if it is not the low-level qualifier. For example, you could enter CCOPC.&XOPCNM..PARMLIB but CCOPC.&XOPCNM.PARMLIB results in a JCL error.
If you enter an asterisk (*) as a data set qualifier, the generated skeletons will contain &XOPCNM. in place of the asterisk.
- Message library name
- Required input. Enter the name of the library that contains the Tivoli Workload Scheduler for z/OS messages (SMP/E target DD name SEQQMSG0).
- Parameter library
- Required input. Enter the name of the library that will contain the initialization statements.
- Member in parameter library
- Required input. Enter the name of a member in the parameter library that will contain the BATCHOPT initialization statement. The Tivoli Workload Scheduler for z/OS batch jobs will use this member. If you have not already created the BATCHOPT statement, you can still generate the batch skeletons, but remember to create a member with the same name when you create the initialization statements.
- Checkpoint data set
- Required input. Enter the name of the checkpoint data set.
- Press Enter, and this panel is displayed:
Figure 18. EQQJOBS2 - Generate Tivoli Workload Scheduler for z/OS batch-job skeletons
EQQJOBS2 ------------ GENERATE TWSz BATCH-JOB SKELETONS ------------------- Command ===> Enter the following required job stream parameters: Non-VSAM dsn prefix ===> CCOPC.*___________________ VSAM dsn prefix ===> CCOPC.*V__________________ Unit name ===> 3390____ Default unit name Unit name (temp ds) ===> SYSDA___ Unit name for temporary data sets Unit name (sort ds) ===> SYSDA___ Unit name for sort work data sets SYSOUT class ===> * SYSOUT class for reports The following information is optional: STEPLIB dsname ===> OPC.SEQQLMD0____________________________________ STEPCAT dsname ===> ________________________________________________ EQQMLOG dsname ===> CCOPC.*.MLOGBAT_________________________________ The following information is REQUIRED WITH DBCS support: KJSRTBL dsname ===> ________________________________________________ Press ENTER to generate OPC batch-job skeletons
- Non-VSAM dsn prefix
- Required input. Enter the qualifiers that prefix the non-VSAM data set names. Tivoli Workload Scheduler for z/OS adds a low-level qualifier to the prefix to uniquely identify the non-VSAM data sets. For example, it adds JTARC for the job-tracking archive data set. If the subsystem name is OPCA, the data set name will be CCOPC.OPCA.JTARC when the skeleton is used by the dialogs.
- VSAM dsn prefix
- Required input. Enter the qualifiers that prefix the VSAM data set names. Tivoli Workload Scheduler for z/OS adds a low-level qualifier to the prefix to uniquely identify each Tivoli Workload Scheduler for z/OS VSAM data set. For example, it adds WS for the workstation description data set. If the subsystem name is OPCA, the data set name will be CCOPC.OPCAV.WS when the skeleton is used by the dialogs.
- Unit name
- Required input. Enter a device name that is valid at your installation. This can be a device type, for example 3380, or a group name, for example PROD or TEST.
- Unit name (temp ds)
- Required input. Enter a device name that can be used for temporary data sets.
- Unit name (sort ds)
- Required input. Enter a device name that can be used for sort-work data sets.
- SYSOUT class
- Required input. Specify the SYSOUT class that you want to use for the reports that are generated by the batch jobs.
- STEPLIB dsname
- Optional. Enter the name of the Tivoli Workload Scheduler for z/OS load module library if the load modules are not in a data set included in an active LNKLST member.
- STEPCAT dsname
- Optional. Enter the name of a private catalog if one or more data sets cannot be reached via the master catalog. To customize the EQQAUDNS skeleton clist with the appropriate loadlib that should be referenced when audit/debug is invoked, you must specify the dsname.
- EQQMLOG dsname
- Optional. Enter the name of a message log data set if messages are not sent to SYSOUT. This must not be the same data set that is used by a tracker, controller, or standby controller.
- KJSRTBL dsname
- Required if you use the Japanese language feature. Enter the name of a data set that will be used when sorting fields containing DBCS data.
- Press Enter. The following panel is displayed:
Figure 19. EQQJOBSA - Generate Tivoli Workload Scheduler for z/OS batch-job skeletons
EQQJOBSA -------------- GENERATE TWSz BATCH-JOB SKELETONS --------------------- Command ===> Specify if you want to use the following optional features: END-TO-END WITH FAULT TOLERANCE: N (Y= Yes ,N= No) (To schedule jobs on fault-tolerant workstations) RESTART AND CLEAN UP (DATA STORE): Y (Y= Yes ,N= No) (To be able to retrieve joblog, execute data set clean up actions and step restart) FORMATTED REPORT OF TRACKLOG EVENTS: N (Y= Yes ,N= No) EQQTROUT dsname ===> ________________________________________________ EQQAUDIT output dsn ===> ________________________________________________ JAVA UTILITIES ENABLEMENT: N (Y= Yes ,N= No) Work Directory ===> /var/TWS/inst___________________________________ ===> ________________________________________________ ===> ________________________________________________ JZOS PDSE Library ===> ________________________________________________ JZOS Load Module Name ===> JVMLDM66 REXX SYSEXEC dsname ===> OPC.SEQQMISC____________________________________ Input XML dsname for ===> TWS.EVLIB.XML($$$$$$$$)_________________________ data set triggering Press ENTER to generate OPC batch-job skeletons
- END-TO-END WITH FAULT TOLERANCE
- Specify Y if you want to work with Tivoli® Workload Scheduler fault-tolerant workstations.
- RESTART AND CLEAN UP (Data Store)
- Specify Y if you want to use the Restart and Cleanup feature.
- FORMATTED REPORT OF TRACKING EVENTS
- Specify Y if you want to use the feature that produces a formatted report of the tracklog events.
- EQQTROUT dsname
- This entry is optional. Specify the name of the data set in which DP Extend and Replan writes tracklog events. Leave blank if you want the corresponding DD card for these jobs to specify DUMMY as in previous releases. Fill out if you plan to use sample EQQAUDIB (see Table 18).
- EQQAUDIT output dsn
- Specify the name of a data set where the EQQAUDIT output is to be written. Required if FORMATTED REPORT OF TRACKLOG EVENTS is set to Y.
- Work Directory
- Specify the directory where the subsystem specific HFS or ZFS files are stored. Each subsystem supporting the JAVA utility must have its own work directory.
- JZOS PDSE Library
- JZOS PDSE Library Specify the PDSE containing the JZOS Batch Launcher JVMLDM module.
- JZOS Load Module Name
- Specify JVMLDM66, that is the JZOS Batch Launcher load module name used with 64-bit SDK for z/OS® 6.0.
- REXX SYSEXEC dsname
- Specify the installation SEQQMISC library containing the REXX programs EQQRXARC and EQQRXTRG.
Note:In controller MLOG dsn, EQQTROUT dsname, and EQQAUDIT output dsn you can use an asterisk (*) for the subsystem name. It will be replaced with the current subsystem name when the dialog is invoked. - Press Enter when you have entered the
information on panel EQQJOBSA. The dialog now generates the batch-job
skeleton members.
After completing this procedure, you can proceed with the creation of the sample job JCL as described in Creating the sample job JCL.
If you are not sure at this stage what some of the values will be, it does not matter. You can rerun the dialog as many times as you want to regenerate the skeletons. You can also edit the generated skeletons manually.
This table shows the JCL skeleton members that EQQJOBS generates:
Member | Batch job description |
---|---|
EQQADCDS | Application cross-reference of conditional dependencies. |
EQQADCOS | Calculate and print run dates of an application. |
EQQADDES | Application cross-reference of external dependencies. |
EQQADPRS | Application print program. |
EQQADXRS | Application cross-reference program. |
EQQADX1S | Application cross-reference of selected fields. |
EQQAMUPS | Application description mass update. |
EQQAPARS | Procedure to gather diagnostic information. |
EQQAUDIS | Extract and format job tracking events (batch invocation). |
EQQAUDNS | Extract and format job tracking events (interactive
invocation)
Note:
Ensure to copy this member from the library
where it was created by EQQJOBS into a procedure library. This step
is required since this member must be invoked interactively. |
EQQDBARS | Daily Planning - Historical run data archiver for Dynamic Workload Console reporting feature |
EQQDPEXS | Daily planning - plan next period. |
EQQDPPRS | Daily planning - print current period results. |
EQQDPRCS | Daily planning - replan current period. |
EQQDPSJS | Daily planning -DBCS sort step. |
EQQDPSTS | Daily planning - normal sort step. |
EQQDPTRS | Daily planning - plan a trial period. |
EQQJVPRS | Print JCL variable tables. |
EQQLEXTS | Long-term planning - extend the long-term plan. |
EQQLMOAS | Long-term planning - modify all occurrences. |
EQQLMOOS | Long-term planning - modify one occurrence. |
EQQLPRAS | Long-term planning - print all occurrences. |
EQQLPRTS | Long-term planning - print one occurrence. |
EQQLTRES | Long-term planning - create the long-term plan. |
EQQLTRYS | Long-term planning - trial. |
EQQOIBAS | Operator instructions - batch program. |
EQQOIBLS | Operator instructions - batch input from a sequential data set. |
EQQSYRES | Daily Planning - Symphony Renew. |
EQQTPRPS | Print periods. |
EQQTPRTS | Print calendars. |
EQQTRBLS | Event driven workload automation - Create configuration files for data set triggering |
EQQWPRTS | Print workstation descriptions. |