Creating the sample job JCL

To ensure that all the 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:

From the EQQJOBS application menu, select option 1. The following panel is displayed:
Figure 1. 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______________________________
 BAtch-job skeletons   ===> ________________________________________________ 

 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     ===> DEV.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 completely qualified and not be enclosed within quotes.

Sample job JCL

Required. Name of the library to which you want that the generated JCL samples are written. 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 (for details, see Sample JCL generated by the EQQJOBS dialog.)

Batch-job skeletons

Required. Name of the library where the JCL skeletons are to be stored (either a new library that you create or an existing JCL skeletons library). Before you submit the batch jobs, allocate this library to the ISPSLIB DD statement in the TSO session of dialog users. For a description about how to set up the dialog, see Step 12. Setting up the ISPF environment.

Job statement information

Required. The JOB statement that follows standard JCL syntax and your installation standards.

Message library name

Required. Name of the library that contains the HCL Workload Automation for Z messages (SMP/E target DDNAME SEQQMSG0).

Data library name

Required. Name of the library that will contain the SSL certificates provided with HCL Workload Automation for Z. For detailed information about these certificates, see Scheduling End-to-end with z-centric Capabilities.

Parameter library

Required. Name of the library that will contain the initialization statements. This library will be allocated by the EQQPCS01 batch job.

Checkpoint data set

Required. Name of the checkpoint data set. This library will be allocated by the EQQPCS01 batch job.
Press Enter. The following panel is displayed:
Figure 2. 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. 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 EV for the event data set. In this example, the full name is CCOPC.OPCA.EV.
Note: HCL Workload Automation for Z does not use the prefix for the parameter library or checkpoint data set. You specified the names of these data sets in the previous panel.

VSAM dsn prefix

Required. The qualifiers that 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 AD for the application description data set. In this example, the complete name is CCOPC.OPCAV.AD.

Unit name

Required. The device name that is valid at your installation; it can be a device type, for example 3380, or a group name, for example PROD or TEST.

Primary volume serial

Required. The volume to be used by sample job EQQPCS01 to allocate the primary data sets. Some HCL Workload Automation for Z 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. The SYSOUT class that you want to use for the reports that are generated by the sample 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.

VSAMCAT dsname

Optional. 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. The password for the VSAM catalog, if the catalog is password-protected.

VSAM files

Optional. The qualifiers that prefix your existing HCL Workload Automation for Z VSAM data set names. These are used to create the data set-conversion sample JCL.

non-VSAM files

Optional. The qualifiers that prefix your existing HCL Workload Automation for Z 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.
Note:

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.

Click Enter. The following panel is displayed:

Figure 3. EQQJOBS9 - Create sample job JCL

EQQJOBS9 ------------------- CREATE SAMPLE JOB JCL ----------------------------
Command ===>                                                                   
                                                                               
  JAVA UTILITIES ENABLEMENT:   Y        (Y= Yes ,N= No)                        
   Installation Directory      ===> /usr/lpp/TWS/V9R5M0_____________________   
                               ===> ________________________________________   
                               ===> ________________________________________   
   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         ===> JVMLDMnn                                   
                                                                               
Press ENTER to continue

JAVA UTILITIES ENABLEMENT

Specify Y to enable one or all the following features:

Dynamic Workload Console reporting.
Event-driven workload automation feature for data set triggering.
Jobs submission on z-centric and dynamic agents.

Installation Directory

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 /bin subdirectory.

Java™ Directory

The HFS or ZFS directory where the Java™ Software Development Kit (SDK) for z/OS® is installed.

Work Directory

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

The UNIX™ System Services user ID.

Group ID

The UNIX™ System Services group ID.

JZOS Batch Launcher PDSE Library

The PDSE that contains the JZOS Batch Launcher JVMLDM module.

JZOS Batch Launcher Load Module Name

Specify JVMLDMnn, meaning the JZOS Batch Launcher load module name used with the 64-bit SDK for z/OS® supported version.

Click Enter. The following panel is displayed:
Figure 4. EQQJOBSC - Create sample job JCL
```
EQQJOBSC ------------------- CREATE SAMPLE JOB JCL ----------------------------
Command ===>                                                                   
                                                                               
                                
  OUTPUT COLLECTOR                  _        (Y= Yes ,N= No)                   
   Class                       ===> ________                                   
   Writer                      ===> ________                                   
                                                                               
  MLOG SWITCH                       _        (Y= Yes ,N= No)                   
   Switchlimit                 ===> _______  (0 , nnnn)

  EXTENDED AUDITING            ===> _        (Y= Yes ,N= No)

  STEP AWARENES                       Y        (Y= Yes ,N= No)            
   Store on primary controller   ===> Y        (Y= Yes ,N= No) forced to N if
                                                Step Awareness is N            
Press ENTER to continue                                            
```
OUTPUT COLLECTOR

If you plan to use the Output collector started task to collect job logs from HCL Workload Automation Agents, specify Y to generate the related samples.

Class

Name of the JES CLASS where the job logs are to be copied by Output collector. If you do not specify this value, no JESCLASS keyword is recorded in the generated EQQOUCP sample; you can define it later in the OUCOPTS initialization statement.

Writer

Name of the user ID associated with the WRITER task used to copy the job logs to the JES SYSOUT. If you do not specify this value, no WRITER keyword is recorded in the generated EQQOUCP sample; you can define it later in the OUCOPTS initialization statement.

MLOG SWITCH

Enter Y if you plan to use the message log (MLOG) switching function, which automatically switches to a second MLOG file when the first one reaches the number of records specified in Switchlimit. Specify Y to generate the related samples.
See also Using two message log (MLOG) data sets.

Switchlimit

The number of records that must be present in the MLOG file to activate the switching function. When this number is reached, the switching function activates an alternate MLOG file and archives the records of the first MLOG file into a GDG data set. You can also use the OPCOPTS SWITCHMLOGLIM parameter to specify or modify this number after the product is installed.
Note that unless you specify a positive number of records, the function is not activated, even if you specified Y in the MLOG SWITCH field. The maximum possible value is 999 999 999 records.
See also Using two message log (MLOG) data sets.

EXTENDED AUDITING

Specify YES to activate the extended auditing feature. This value is meaningful only if you have set AMOUNT(EXTENDED) in the AUDIT statement of the controller.
By activating the extended auditing feature, the EQQPCS14 sample creates the EQQDBnn, EQQDBARC, and EQQDBOUT data sets. EQQDBnn and EQQDBARC are added to the controller started-task. EQQDBARC and EQQDBOUT are added to the DP batch job.

STEP AWARENESS

Specify YES to have the tracker generate a list of the step events related to the jobs you run, and send it to the primary controller. The primary controller logs the step list, without storing it. If a backup controller exists, the primary controller sends the list to the backup controller, where the information is stored.

Store on primary controller

Specify YES to store the list of step events also on the primary controller. This option can affect the controller performance.
Click Enter. The following panel is displayed:
Figure 5. EQQJOBSD - Create sample job JCL
```
EQQJOBSD ------------------- CREATE SAMPLE JOB JCL ----------------------------
Command ===>                                                                   
  
  CDP LOG INTEGRATION ENABLEMENT:    Y  (Y= Yes ,N= No)
   HFS Path for log files      ===>  /u/cdplog______________________________
   Switch CDP log limit        ===>  12000  (1, nnnnnnnn)
    (Switch limit is an integer representing the number of records to be 
      written in current LOG before to switch to the second, default is 1000)
                                                                           
  BKPT configuration           N        (Y= Yes ,N= No)                        
   Backup data set name        ===> TWSZ.INST.BKPT__________________________   
                                                                                  
  BKPTOPTS statement procedure names:                                          
   DUMP Procedures for:                                                        
   NCP, NCX, NXD Files         ===> ________       CX, CP1, XD1 Files      ===> ________                                   
   LTP File                    ===> ________       CX, CP2, XD2 Files      ===> ________                                   

   RESTORE Procedures:                                                         
   NCP, NCX, NXD Files         ===> ________       CX, CP1, XD1 Files      ===> ________                                   
   LTP FIle                    ===> ________       CX, CP2, XD2 Files      ===> ________                                   
   
 Press ENTER to create sample job JCL.                                            
```
CDP LOG INTEGRATION ENABLEMENT

Enter Y to enable the logging of data in the EQQCDP1 and EQQCDP2 log files, which are read by IBM Common Data Provider for z Systems (CDP) if you configure it to integrate with HCL Workload Automation for Z.

HFS Path for log files

The complete path to the EQQCDP1 and EQQCDP2 log files (up to 40 alphanumeric characters). It must be existent in the HFS file system.

Switch CDP log limit

How many records must be written in the CDP log, before the CDP log switching function is started. The CDP log switching function stops the running CDP log file, and starts the alternate CDP log file. The alternate CDP log file records upcoming messages until the log limit value is reached again, and the process is repeated.
The default is 1000. Valid values are between 1 and 999 999 999.

BKPT configuration

Specify Y to enable the backup controller configuration.

Backup data set name

Required. The name of the backup data set.

DUMP Procedures for NCP, NCX, NXD Files

Name of the dump procedure for NCP, NCX, and NXD files. If you do not specify any value, the default EQQSENCP is used.

DUMP Procedures for CX, CP1, XD1 Files

Name of the dump procedure for CX, CP1, XD1, and ST files. If you do not specify any value, the default EQQSECP1 is used.

DUMP Procedures for CX, CP2, XD2 File

Name of the dump procedure for CX, CP2, XD2, and ST files. If you do not specify any value, the default EQQSECP2 is used.

DUMP Procedures for LTP Files

Name of the dump procedure for the LTP file. If you do not specify any value, the default EQQSENLT is used.

RESTORE Procedures for NCP, NCX, NXD Files

Name of the restore procedure for NCP, NCX, and NXD files. If you do not specify any value, the default EQQRENCP is used.

RESTORE Procedures for CX, CP1, XD1 Files

Name of the restore procedure for CX, CP1, XD1, and ST files. If you do not specify any value, the default EQQRECP1 is used.

RESTORE Procedures for CX, CP2, XD2 Files

Name of the restore procedure for CX, CP2, XD2, and ST files. If you do not specify any value, the default EQQRECP2 is used.

RESTORE Procedures for LTP File

Name of the restore procedure for the LTP file. If you do not specify any value, the default EQQRESLT is used.
After you have entered the information on panel EQQJOBSD, click Enter. The dialog process generates several members in the output library that you specified. These members, which are described in Sample JCL generated by the EQQJOBS dialog, will be used at various stages of the installation.

Table 1. Sample JCL generated by the EQQJOBS dialog
Member	Description of job
EQQ9SM01	Updates the RACF® router table (ICHRFR01).
EQQ9SMDE	Updates the RACF® class-descriptor table (ICHRRCDE).
EQQAUDIB	Sample to invoke EQQAUDIT in batch mode outside of the dialog. Note: EQQAUDIB is used only if you specified a value for the EQQTROUT dsname and the EQQAUDIT output dsn fields in the EQQJOBSA panel.
EQQBENCR	Sample JCL to run the utility that encrypts the Windows™ passwords set in the USRPSW parameter of the USRREC statements.
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.
EQQFLWAT	Sample JCL to call filewatch utility to monitor HFS or ZFS file changes.
EQQICNVS	Migrates VSAM files.
EQQICVFY	Verifies that the CP records are not corrupted. If they are, it repairs the First Operations (FOPs) and Last Operations (LOPs) in the CP3C VSAM record.
EQQJES2	Assembles and link-edits the JES2 EXIT7.
EQQJER2U	Restores the EXIT7 as a JES2 usermod.
EQQJER2V	Restores the EXIT51 as a JES2 usermod.
EQQJER3U	Restores the EQQUX191 and EQQUX291 as JES3 usermods.
EQQJER3Z	Restore the EQQUX291 as JES3 usermod.
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.
EQQJES3Z	Installs the EQQUX291 as JES3 usermod.
EQQOUC	Sample started task procedure for the Output collector.
EQQOUCH	Sample header template for job logs.
EQQOUCP	Sample initial parameters for the Output collector.
EQQPCS01	Allocates unique data sets within the sysplex.
EQQPCS02	Allocates non-unique data sets.
EQQPCS03	Generates a job that allocates VSAM copy data set.
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.
EQQPCS11	Allocates data sets (EQQOUCEV and EQQOUCKP) used for the retrieval of job logs in the z-centric environment with the Output collector.
EQQPCS12	Allocates the GDG root to archive the MLOG files.
EQQPCS13	Allocates the GDG root to send and restore procedures.
EQQPCS14	Allocates the data sets for the extended auditing.
EQQRECP1	Restore procedure for CX, CP1, XD1, ST files.
EQQRECP2	Restore procedure for CX, CP2, XD2, ST files.
EQQRENCP	Restore procedure for NCP, NCX, NXD files.
EQQRESLT	Restore procedure for LTP files.
EQQREPRO	Is invoked by EQQSMLOG to copy the contents of the outgoing MLOG file onto the GDG data set. You must copy this sample to the PARMLIB of the controller.
EQQRAD	Restore procedure for the Application Description.
EQQRJS1	Restore procedure for the primary JCL repository.
EQQRJS2	Restore procedure for the secondary JCL repository.
EQQROI	Restore procedure for the Operator Instructions.
EQQRRD	Restore procedure for the Resource Description.
EQQRSI	Restore procedure for the Side Information file.
EQQRWS	Restore procedure for the Workstation Description.
EQQSAD	Send procedure for the Application Description.
EQQSAMPI	Copies sample databases from the sample library to VSAM data sets.
EQQSECP1	Dump procedure for CX, CP1, XD1, ST files.
EQQSECP2	Dump procedure for CX, CP2, XD2, ST files.
EQQSENCP	Dump procedure for NCP, NCX, NXD files.
EQQSENLTP	Dump procedure for LTP files.
EQQSERP	Sample initial parameters for a Server.
EQQSER	Sample started task procedure for a Server.
EQQSJS1	Send procedure for the primary JCL repository.
EQQSJS2	Send procedure for the secondary JCL repository.
EQQSMF	Updates SMF exits for HCL Workload Automation for Z.
EQQSMLOG	Sample procedure that creates the GDG data set where the outgoing MLOG file is archived when the MLOG switching function takes effect. Uses the EQQREPRO input parameter.
EQQSOI	Send procedure for the Operator Instructions.
EQQSRD	Send procedure for the Resource Description.
EQQSSI	Send procedure for the Side Information file.
EQQSWS	Send procedure for the Workstation Description.
EQQTRA	Sample started task procedure for a tracker.
EQQTRAP	Sample initial parameters for a tracker.
EQQTROPT	Sample TRGOPT statement.