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.
- From the EQQJOBS main menu, select option 2. The following panel is displayed:
Ensure that &XOPCNM. ends with a period if it is not the low-level qualifier. For example, you could enter
- Batch-job skeletons
- Required. Name of the library where the JCL skeletons are to be stored. Before
you use the HCL Workload Automation for Z dialog
to submit batch jobs, allocate this library to the ISPSLIB DD statement in the
TSO session of dialog users.
For detailed information about how you set up the dialog, see The ISPF environment. You can create a new library for the skeleton JCL members or put them in an existing skeleton-JCL library.
CCOPC.&XOPCNM..PARMLIB
butCCOPC.&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. Name of the library that contains the HCL Workload Automation for Z messages (SMP/E target DD name SEQQMSG0).
- Parameter library
- Required. Name of the library where to store the initialization statements.
- Member in parameter library
- Required. Name of a member in the parameter library where to store the BATCHOPT initialization statement. The HCL Workload Automation for Z 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. Name of the checkpoint data set.
- Click Enter. The following panel is displayed:
- Non-VSAM dsn prefix
- Required. Enter the qualifiers that prefix the non-VSAM data set names. HCL Workload Automation for Z 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. Enter the qualifiers to prefix the VSAM data set names. HCL Workload Automation for Z adds a low-level qualifier to the prefix to uniquely identify each HCL Workload Automation for Z 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. 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. Enter a device name that can be used for temporary data sets.
- Unit name (sort ds)
- Required. Enter a device name that can be used for sort-work data sets.
- SYSOUT class
- Required. Specify the SYSOUT class that you want to use for the reports that are generated by the batch jobs.
- STEPLIB dsname
- Optional. Name of the HCL Workload Automation for Z load module library if the load modules are not in a data set included in an active LNKLST member.
- STEPCAT dsname
- Optional. Name of a private catalog if one or more data sets cannot be reached through 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. 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. Name of the data set to be used when sorting fields containing DBCS data.
- Click Enter. The following panel is displayed:
- 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
- Optional. 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. Type out if you plan to use sample EQQAUDIB (see Sample JCL generated by the EQQJOBS dialog).
- EQQAUDIT output dsn
- Name of the data set where the EQQAUDIT output is to be written. Required if FORMATTED REPORT OF TRACKLOG EVENTS is set to Y.
- Work Directory
- 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
- The PDSE containing the JZOS Batch Launcher JVMLDM module.
- JZOS Load Module Name
- Specify JVMLDMnn, meaning the JZOS Batch Launcher load module name used with the 64-bit SDK for z/OS® supported version.
- REXX™ SYSEXEC dsname
- The installation SEQQMISC library containing the REXX™ programs EQQRXARC and EQQRXTRG.
- Input XML dsname for data set triggering
- Name of the input data set containing the event rules in XML format used to produce the data set triggering configuration files that will be sent to trackers. The default data set is provided in the panel.
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. - After you have entered the information on panel EQQJOBSA, click Enter. The dialog
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.
Controller skeleton JCL generated by the EQQJOBS dialog shows the JCL skeleton members generated by EQQJOBS:
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. |
EQQTPRPS | Print periods. |
EQQTPRTS | Print calendars. |
EQQTRBLS | Event driven workload automation - Create configuration files for data set triggering |
EQQWPRTS | Print workstation descriptions. |