Creating the sample job JCL
To ensure that all files are correctly allocated, before creating the sample job JCL you must have generated the batch-job skeletons as described in Generating batch-job skeletons.
To create the sample job JCL:
- Select option 1 from the EQQJOBS application menu. This panel
is displayed:
Figure 12. EQQJOBS3 - Create sample job JCL
EQQJOBS3 ------------------- CREATE SAMPLE JOB JCL ---------------------------- Command ===> The data set names specified on this panel should be fully qualified names without any enclosing apostrophes. Enter the name of the output library: Sample job JCL ===> CCOPC.OPCA.INSTJCL______________________________ Job statement information: ===> //SYSPROG1 JOB (111111,2222),'OPCESA BATCH',CLASS=B,MSGCLASS=H,_______ ===> // MSGLEVEL=(1,1),NOTIFY=SYSPROG______________________________ ===> //*___________________________________________________________________ ===> //*___________________________________________________________________ The following data set names are used by one or more of the generated job Message library name ===> OPC.SEQQMSG0____________________________________ Data library name ===> TWSDEV.DATA_____________________________________ Parameter library ===> CCOPC.OPCA.PARM_________________________________ Checkpoint data set ===> CCOPC.OPCA.CKPT_________________________________ Press ENTER to continue
The data set names that you specify on this panel must be fully-qualified and not be enclosed within apostrophes.
- Sample job JCL
- Required input. Enter the name of a library where you want the generated JCL samples written to. The library must be allocated before you generate the batch JCL samples. Ensure that the library that you specify has sufficient directory blocks to store all the sample members that are generated by EQQJOBS (see Table 18.)
- Job statement information
- Required input. Enter a JOB statement that follows standard JCL syntax and your installation standards.
- Message library name
- Required input. Enter the name of the library that contains the Tivoli Workload Scheduler for z/OS messages (SMP/E target DDNAME SEQQMSG0).
- Data library name
- Required input. Enter the name of the library that will contain the SSL certificates that are provided with Tivoli Workload Scheduler for z/OS. For detailed information about these certificates, see the Tivoli Workload Scheduler for z/OS: Scheduling End-to-end with z-centric Capabilities manual.
- Parameter library
- Required input. Enter the name of a library that will contain the initialization statements. This library will be allocated by the EQQPCS01 batch job.
- Checkpoint data set
- Required input. Enter the name of the checkpoint data set. This library will also be allocated by the EQQPCS01 batch job.
- Press Enter, and this panel is displayed:
Figure 13. EQQJOBS4 - Create sample job JCL
EQQJOBS4 ------------------- CREATE SAMPLE JOB JCL ---------------------------- Command ===> Enter the following required job stream parameters: non-VSAM dsn prefix ===> CCOPC.OPCA________________ VSAM dsn prefix ===> CCOPC.OPCAV_______________ Unit name ===> 3390____ Default unit name Primary volume serial ===> PROD01 Primary volume serial for VSAM Backup volume serial ===> PROD02 Secondary volume serial for VSAM SYSOUT class ===> * SYSOUT class for reports The following information is optional: STEPLIB dsname ===> OPC.SEQQLMD0____________________________________ VSAMCAT dsname ===> ________________________________________________ VSAM password ===> ________ Dsn prefix of old VSAM files ===> CCOPC.OPCAV_______________ non-VSAM files ===> CCOPC.OPCA________________ Samples with cloning support generated: N (Y/N) Static symbol used ===> SYSCLONE without enclosing ‘&’ and period Press ENTER to continue
- 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
EV for the event data set. In this example, the full name is CCOPC.OPCA.EV.
Note:Tivoli Workload Scheduler for z/OS does not use the prefix for the parameter library or checkpoint data set. You entered the names of these data sets, fully qualified, on the previous panel.
- 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 AD for the application description data set. In this example, the full name is CCOPC.OPCAV.AD .
- Unit name
- Required input. Enter a device name that is valid at your installation. This could be a device type, for example 3380, or a group name, for example PROD or TEST.
- Primary volume serial
- Required input. Enter a volume to be used by sample job EQQPCS01 to allocate the primary data sets. Some Tivoli Workload Scheduler for z/OS logical files are implemented as two physical data sets, a primary and an alternate; for example, the current plan data set. To minimize the potential impact of errors on a particular device, allocate the primary and alternate data sets on different physical devices.
- SYSOUT Class
- Required input. Enter the SYSOUT class that you want to use for the reports that are generated by the sample 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.
- VSAMCAT dsname
- Optional. Enter the name of a catalog in which VSAM data sets are to be defined if they are not to be defined in the master catalog.
- VSAM password
- Optional. Enter the password for the VSAM catalog if the catalog is password-protected.
- VSAM files
- Optional. Enter the qualifiers that prefix your existing Tivoli Workload Scheduler for z/OS VSAM data set names. These are used to create the data set-conversion sample JCL.
- non-VSAM files
- Optional. Enter the qualifiers that prefix your existing Tivoli Workload Scheduler for z/OS non-VSAM data set names. These are used to create the data set-conversion sample JCL.
- Samples with cloning support generated
- Optional. Enter Y if you want the SYSCLONE variable resolved.
Notes:
- Generated JCLs do not contain a period before &SYSCLONE.
- &SYSCLONE variable is intended to be substituted in the scheduler started tasks. It is not substituted in the generated JCLs that run as batch jobs. To obtain the variable substitution, run the JCL as cataloged procedure.
- Press Enter. The following panel is displayed:
Figure 14. EQQJOBS8 - Create sample job JCL
EQQJOBS8 ------------------- CREATE SAMPLE JOB JCL -------------------------- Command ===> END-TO-END WITH FAULT TOLERANCE: Y (Y= Yes ,N= No) Installation Directory ===> /usr/lpp/TWS/V8R5M0_____ ===> ______________________________ ===> ______________________________ Work Directory ===> /var/TWS/inst_________________ ===> ______________________________ ===> ______________________________ User for OPC address space ===> UID_ Refresh CP group ===> GID__ RESTART AND CLEANUP (Data Store) Y (Y= Yes ,N= No) Reserved destination ===> OPCX____ Connection type ===> SNA (SNA/XCF/TCP) SNA Data Store luname ===> I9PC45AA (only for SNA connection ) SNA FN task luname ===> I9PC45RA (only for SNA connection ) Xcf Group ===> ________ (only for XCF connection ) Xcf Data Store member ===> ________ (only for XCF connection ) Xcf FL task member ===> ________ (only for XCF connection ) TCP Data store host name: (only for TCP connection ) ===> ____________________________________________________ TCP Data store port number ===> _____ (only for TCP connection ) Press ENTER to continue
- END-TO-END WITH FAULT TOLERANCE
- Specify Y if you want to schedule jobs on fault-tolerant agent
workstations.
Only the Server requires a UID and a GID. Set the UID to a nonzero value, unless you plan to run the EQQPCS05 sample JCL.
- Installation Directory
-
Specify the path where SMP/E has installed the Tivoli® Workload Scheduler for z/OS® files for UNIX system services that apply the end-to-end enabler feature. This directory is the one containing the bin directory. The default path is /usr/lpp/TWS/VvRrMm.
- Work Directory
- Specify where the subsystem-specific files are. Replace /inst with a name that uniquely identifies your subsystem. Each subsystem that will use the fault-tolerant workstations must have its own work directory. Only the server and the daily planning batch jobs go in the work directory. See Allocating the files and directories.
- User for OPC address space
- This information is used to create the procedure to build the directory with the right ownership. To run the end-to-end scheduling with fault tolerance capabilities correctly, the ownership of the work directory, and the files it contains, must be assigned to the same user ID that RACF® associates with the Server Started Task. In the User for OPC address space field, specify the RACF user ID used for the Server address space. This is the name specified in the started-procedure table.
- Refresh CP group
- This information is used to create the procedure to build the directory with the right ownership. To create the new Symphony file, the user ID used to run the daily planning batch job must belong to the group that you are specifying in this field. Also ensure that the user ID associated with the Server address space (the one specified in User for OPC address space field) belongs to this group or has this group as supplementary group.
- RESTART AND CLEANUP (Data Store)
- Specify Y if you want to use the Restart and Cleanup function.
Note:The panel shown in Figure 14 creates only one sample entry, but you can define all kinds of connections, including a combination of mixed connections.
- Reserved destination
- Specify the destination reserved for Data Store output. It must be the same as that for controller and Data Store parameters.
- Connection type
- Specify the connection method used to handle communication between FN/FL tasks and Data Store. It can be SNA, XCF, or TCP. Required.
- SNA Data Store luname
- If you chose SNA in Connection type, specify the Data Store VTAM® connection name.
- SNA FN task luname
- If you chose SNA in Connection type, specify the VTAM application name of the controller FN task.
- Xcf Group
- If you chose XCF in Connection type, specify the name of the XCF group.
- Xcf Data Store member
- If you chose XCF in Connection type, specify the name of the Data Store XCF member.
- Xcf FL task member
- If you chose XCF in Connection type, specify the name of the controller FL task XCF member.
- TCP Data store host name
- Specify the Data Store TCP/IP host name if you chose TCP in Connection type.
- TCP Data store port number
- Specify the Data Store TCP/IP port number if you chose TCP in Connection type.
- Press Enter. The following panel is displayed:
Figure 15. EQQJOBS9 - Create sample job JCL
EQQJOBS9 ------------------- CREATE SAMPLE JOB JCL ---------------------------- Command ===> JAVA UTILITIES ENABLEMENT: Y (Y= Yes ,N= No) Installation Directory ===> /usr/lpp/TWS/V8R5M0_____________________ ===> ________________________________________ ===> ________________________________________ Java Directory ===> /usr/lpp/java/J5.6______________________ ===> ________________________________________ ===> ________________________________________ Work Directory ===> /var/TWS/inst___________________________ ===> ________________________________________ ===> ________________________________________ User ID ===> UID_____ Group ID ===> GID_____ JZOS Batch Launcher PDSE Library ===> ___________________________________________ Load Module Name ===> JVMLDM66 Press ENTER to continue
- JAVA UTILITIES ENABLEMENT
- Specify Y to enable one or both the following
features:
- Dynamic Workload Console reporting
- Event-driven workload automation feature for data set triggering
- Installation Directory
- Specify the directory, with its complete path, where the product specific HFS or ZFS files are stored. This path corresponds to the path where the binary files are located, omitting the subdirectory /bin.
- Java Directory
- Specify the HFS or ZFS directory where the Java Software Development Kit (SDK) for z/OS is installed.
- 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.
- User ID
- Specify the UNIX System Services user ID.
- Group ID
- Specify the UNIX System Services group ID.
- JZOS Batch Launcher PDSE Library
- Specify the PDSE that contains the JZOS Batch Launcher JVMLDM module.
- JZOS Batch Launcher Load Module Name
- Specify JVMLDM66, that is the JZOS Batch Launcher load module name used with 64-bit SDK for z/OS 6.0.
- Press Enter. The following panel is displayed:
Figure 16. EQQJOBSC - Create sample job JCL
EQQJOBSC ------------------- CREATE SAMPLE JOB JCL ---------------------------- Command ===> SSL FOR TCP/IP CONNECTION Y (Y= Yes ,N= No) SSL Work Directory ===> /var/TWS/inst/ssl_______________________ ===> ________________________________________ ===> ________________________________________ SSL User ID ===> UID_____ SSL Group ID ===> GID_____ Press ENTER to create sample job JCL
- SSL FOR TCP/IP CONNECTION
- Specify Y if you have trackers connected to the controller through TCP/IP to protect the communication with SSL.
- SSL Work Directory
- Specify the directory, with its complete path, where the HFS or ZFS files containing the SSL certificates are stored. The default value is the same work directory used for the fault-tolerant end-to-end scheduling, including the /ssl subdirectory.
- SSL User ID
- Specify the RACF user ID that takes the ownership of the SSL work directory. The default value is the same user ID specified for the fault-tolerant end-to-end scheduling.
- SSL Group ID
- Specify the RACF group that takes the ownership of the SSL work directory. The default value is the same group specified for the fault-tolerant end-to-end scheduling.
- Press Enter when you have entered the information on panel EQQJOBSC. The dialog process now generates several members in the output library that you specified. These members, which are described in Table 18, will be used at various stages in the installation.
Member | Description of job |
---|---|
EQQ9SM01 | Updates the RACF 1.9 router table (ICHRFR01) |
EQQ9SMDE | Updates the RACF 1.9 class-descriptor table (ICHRRCDE) |
EQQAUDIB | Sample to invoke EQQAUDIT in batch mode outside
of the dialog
Note:
EQQAUDIB can be used successfully only
if the EQQTROUT dsname and the EQQAUDIT
output dsn fields in the EQQJOBSA panel are filled in |
EQQBENCR | Sample JCL to run the utility that encrypts the Windows passwords set in the USRPSW parameter of the USRREC statements. |
EQQBSCAN | Uses the batch loader to scan an application description |
EQQBSUBS | Uses the batch loader to create the application descriptions and operator instructions |
EQQBVSAM | Deletes and defines an application description data set and creates an application description and operator instructions, using the batch loader |
EQQCHKEV | Utility that checks if all events in EQQTWSIN and EQQTWSOU have been correctly processed |
EQQCONOP | Sample initial parameters for the controller only |
EQQCONO | Sample started task procedure for the controller only |
EQQCONP | Sample initial parameters for a controller and tracker in same address space |
EQQCON | Sample started task procedure for a controller and tracker in same address space |
EQQDBENC | Contains the JCL to encrypt the password in the DBOPT statement |
EQQDBOPT | Sample DBOPT statement |
EQQDPCOP | JCL and usage notes for copy VSAM function |
EQQE2EP | Sample initial parameters for server and batch to define if the end-to-end scheduling with fault tolerance capabilities is active |
EQQFLWAT | Sample JCL to call filewatch utility to monitor HFS or ZFS file changes |
EQQICNVH | Sample job to migrate history DB2® tables |
EQQICNVS | Migrates VSAM files |
EQQJES2 | Assembles and link-edits the JES2 EXIT7 |
EQQJER2U | Restores the EXIT7 as a JES2 usermod |
EQQJER2V | Restores the EXIT5 as a JES2 usermod |
EQQJER3U | Restores the EQQUX191 and EQQUX291 as JES3 usermods |
EQQJES21 | Assembles and link-edits the JES2 EXIT51 |
EQQJES2U | Installs the JES2 EXIT7 usermod |
EQQJES2V | Installs the JES2 EXIT51 usermod |
EQQJES3 | Assembles and link-edits a JES3 exit |
EQQJES3U | Installs the JES3 usermod |
EQQMTWSO | Migrates TWSOU data set size for extended job names from lrecl 120 to lrecl 160 |
EQQORST | Resets the USS environment for the end-to-end scheduling with fault tolerance capabilities |
EQQPCS01 | Allocates unique data sets within the sysplex |
EQQPCS02 | Allocates non-unique data sets |
EQQPCS03 | Generates a job that allocates VSAM copy data set |
EQQPCS05 | Allocates files used by a controller to enable Fault Tolerant Workstations |
EQQPCS06 | Allocates VSAM data sets for integration with the end-to-end scheduling with fault tolerance capabilities |
EQQPCS07 | Allocates VSAM data sets for Restart and Cleanup |
EQQPCS08 | Allocates USS files for Java utilities enablement |
EQQPCS09 | Allocates the GDG root and VSAM data set used as input by the archiving process supporting the Dynamic Workload Console reporting feature |
EQQPCS10 | Creates the SSL work directory used for TCP/IP communication with the controller |
EQQSAMPI | Copies sample databases from the sample library to VSAM data sets |
EQQSERP | Sample initial parameters for a Server |
EQQSER | Sample started task procedure for a Server |
EQQSLCHK | JCL to perform a syntactic check on SCRIPT library members |
EQQSMF | Updates SMF exits for Tivoli Workload Scheduler for z/OS |
EQQTRA | Sample started task procedure for a tracker |
EQQTRAP | Sample initial parameters for a tracker |
EQQTROPT | Sample TRGOPT statement |