Mass Job Rename Utility › Mass Job Rename Procedure

Mass Job Rename Procedure

Each of the CA Workload Automation SE Mass Job Rename processes uses sequential backups of their respective databases as input. A user-defined control file describing the old and new job names is also supplied as input. The output is a sequential file with altered job names that is suitable for reload.

To perform a mass job rename

1. Create a RENAMES control file defining the job names to be changed with their corresponding new names. The same RENAMES control file will be used for all rename processors to ensure that the changes are consistent across all elements.
2. Shut down CA Workload Automation SE with a DMPQ option to create a backup of the CA Workload Automation SE queues.
3. Create a backup file of the file created from the DMPQ operation (the data set name is found in the UCC7QDMP DD statement of CA7ONL). This is used as input to the queue renames processor (Step 8).
4. Create a sequential backup of the CA Workload Automation SE database using IDCAMS or SASSBK00.
5. Optionally, create a sequential backup of the CA Workload Automation SE VRM file using IDCAMS.
6. Optionally, create a sequential backup of the CA Workload Automation SE ARF file using IDCAMS.
7. Tailor and run the database rename processor, CAL2JRXD, to create an altered sequential backup of the CA Workload Automation SE database.
8. Tailor and run the queue rename processor, CAL2JRXQ, to create an altered sequential backup of the CA Workload Automation SE queues. The output file from this step is used in the MOVQ operation (Step 14).
9. Optionally, tailor and run the VRM rename processor, CAL2JRXV, to create an altered sequential backup of the CA Workload Automation SE VRM database.
10. Optionally, tailor and run the ARF rename processor, CAL2JRXA, to create an altered sequential backup of the CA Workload Automation SE ARF database.
11. Reload the CA Workload Automation SE database with the altered sequential backup (created in Step 7) using IDCAMS or SASSBK00.
12. Optionally, reload the CA Workload Automation SE VRM file with the altered sequential backup (created in Step 9) using IDCAMS. To reload the VRM database, you may choose to use CA07N516 job in JCLLIB or the JCL procedure CA7VRL.
13. Optionally, reload the CA Workload Automation SE ARF file with the altered sequential backup (created in Step 10) using IDCAMS. To reload the ARF database, you may choose to use CA07N518 job in JCLLIB or the JCL procedure CA7ARL.
14. Start CA Workload Automation SE using the MOVQ option to reload the queues from the altered sequential backup (created in Step 8).

    Note: If IDCAMS is used to back up the CA Workload Automation SE database, there should be three files that are used to rename jobs on the SASDS, SASJOB, and IDS data sets. Thus, Steps 4, 7, and 11 would be executed for each of the data sets forming the database. Also, if IDCAMS is used, when reloading the database and/or VRM database, ensure that the data set has been deleted and redefined. If not, IDCAMS issues "duplicate keys" messages during the reload.

15. Review global variables, if any. Check names, values, and masks to determine whether any need to be changed. Use the /GVAR command to either modify global variables or delete and add global variables as appropriate.