All the sample jobs that are used with the IBM Tivoli Workload Scheduler for z/OS job management include the required control statements about recovery, restart, or modifications to make at submit time. The JCL uses procedures that are provided to avoid duplicate JCL and to simplify job construction.

Preparation

You must first allocate files that are required for the regular processing. EDGHSKP has special requirements for the data sets that are used for processing. Use EDGJHKPA to define the GDGs and set up the first generation of the files as required. EDGJHKPA uses the procedures EDGPHKPA, EDGPVRSA, EDGPMSGA, EDGPACTA and EDGPRPTA, and REXX procedure EDGRHKPA. Specify parameters in EDGHKPA to customize the GDG names and limits. Customize the file size by altering the SPACE values in the lowest level procedures.

The GDGMODEL should be customized to match a model DSCB available on your system. Any DCB attributes are acceptable because DFSMSrmm overrides the values at OPEN time. For system-managed data sets, a model DSCB name is not required, and you can specify GDGMODEL='' in that case.

CDS Verify

Run this job when you want to verify the contents of the DFSMSrmm control data set. The EDGJVFY job runs EDGUTIL with PARM=VERIFY on the current DFSMSrmm control data set. The expected completion is return code 0. You must perform manual recovery before dependent jobs can be run when the return code is greater than 0.

CDS Backup

Run this job when you want to back up the DFSMSrmm control data set. The EDGJBKP1 and EDGBKP2 jobs run EDGHSKP with PARM=BACKUP. Backup is performed at the start and at the end of the main inventory management application processing. You can modify the jobs to use DFSMSdss or AMS for backup. You make the choice of backup to DASD or tape when running the preparation jobs.

Jobs EDGJBKP1 and EDGJBKP2 run procedure EDGPBKP to perform the backup. Expected completion is return code 4 or less. You must perform manual recovery before dependent jobs can be run when the return code is greater than 4.

Inventory Management

Run this job when you want to perform DFSMSrmm inventory management processing. These jobs run EDGHSKP with VRSEL and EXPROC. These jobs also include running storage location management on a weekly basis to trigger movement decisions for off-site storage. Job EDGJDHKP and job EDGJWHKP run procedures EDGPHSKP, EDGPMSGA, and EDGPVRSA to process and set up the files for the next run. The job copies the message file to SYSOUT for easier information analysis. The expected completion is return code 4 or less. You must perform manual recovery before dependent jobs can be run when the return code is greater than 4. As part of the recovery, run the EDGJVRSV job to run VRSEL with VERIFY and to report on the ACTIVITY file for analysis of VRSMIN and VRSCHANGE conditions. For return code 8, you might have to change vital record specifications or add additional empty bin numbers. Higher return codes or abends need to be researched by the support programmer.

Erasing and Labeling Volumes

Run this job when you want to initialize and erase volumes depending on the release actions set for the volumes. The EDGJINER job runs an automatic EDGINERS job to handle the INIT and ERASE release actions. You can run dependent jobs that are run regardless of successful completion.

Scratch Processing

Run this job when you want to process volumes that are returning to scratch status. The EDGJSCR job runs EDGHSKP with the EXPROC parameter. This job handles the return to scratch of volumes requiring confirmed actions; whether INIT/ERASE or movement actions. You can run dependent jobs regardless of successful completion.

Scratch Reporting

Run this job when you want to obtain information about volumes in scratch status. The EDGJSCR job produces an up-to-date extract and uses EDGRPTD with SCRLIST and NEWSCR files to produce the latest scratch list reports. You can run dependent jobs regardless of successful completion.

Ejecting Volumes

Run this job to eject volumes from system-managed tape libraries. This is an optional job that you can use if your installation uses system-managed tape. The job also includes support for VTS export processing. You can run dependent jobs regardless of successful completion. You can customize this job to include similar processing that is required for any non-system-managed volumes that you have in your library.

Producing Reports

Run this job to produce volume movement reports. The EDGJMOVE job is dependent on the inventory management job and optionally the ejecting volume job processing. This job creates an up-to-date extract and uses EDGRPTD to produce the movement reports. You can run dependent jobs regardless of successful completion.

Move Confirmation

Run this job to perform global confirmation of volume movement. The EDGJCMOV job issues a global confirm move. You can run this job after a manual action is taken by the installation to mark the movement complete at the dependent IBM Tivoli Workload Scheduler for z/OS workstation. You can run dependent jobs regardless of successful completion.

Daily jobs are always run on processing days. Weekly and monthly jobs are included in the job flow and the IBM Tivoli Workload Scheduler for z/OS automatically adjusts dependencies that are based on the rules you specify. When a job fails, the IBM Tivoli Workload Scheduler for z/OS automatically prevents dependent jobs from processing if any manual recovery actions have been defined. To alter the dependencies, you can modify the sample IBM Tivoli Workload Scheduler for z/OS applications that are described in IBM Tivoli Workload Scheduler for z/OS applications for DFSMSrmm.

CDS backup and scratch processing are functions that are always run in the daily cycle. CDS backup and scratch processing can also be added dynamically to the cycle as required. When CDS backup and scratch processing are added dynamically, they run independently. They are added automatically to the schedule when the write-to-operator (WTO) from DFSMSrmm is detected and the BACKUPPROC or SCRATCHPROC is triggered. When a started procedure matches an application defined to the IBM Tivoli Workload Scheduler for z/OS running on a started task processor, IBM Tivoli Workload Scheduler for z/OS modifies the current plan.