Previous Topic: Mass Job Rename UtilityNext Topic: Mass Job Rename Procedure


Overview

The Mass Job Rename Utility consists of several batch processes that can change job names in all places where they appear in the CA Workload Automation SE database and queue files. This includes all indirect references to job names such as job predecessors, job prose, ending job names in CPM Flow definitions that are defined as of VRM Corequisite resources, and so forth. These utilities can be used to rename large numbers of job names at the same time with a single run of the utility jobs to ensure that all components of CA Workload Automation SE remain synchronized.

The following processes make up the Mass Job Rename Utility:

You can obtain a preview of the changes by submitting the jobs and having the output specified as DD DUMMY,DCB=(data). The preview shows all areas where the job name was found and the new name that will be used. This way, you can review all changes prior to executing the process that updates the CA Workload Automation SE databases. It is important that all four utilities, if VRM and ARF used, are executed against the current backup files concurrently or in the same time period before CA Workload Automation SE is brought back into the system. Failure to execute the Queues Rename utility may cause missing requirements for future jobs once CA Workload Automation SE is brought back into the system.

The SUMMARY DD statement is optional for each of the utilities. If the SUMMARY DD statement is not coded, the summary report is included in the SYSPRINT DD output. The data is separated should the installation want to direct the report summary to a different location.

For specific details about the elements that can be changed through this process, see the subsequent sections in this chapter.

Note: The Mass Job Rename utilities do not examine any JCL libraries. As a result, job names that are used in the Batch Terminal Interface (BTI) programs, such as SASSTRLR and U7SVC, are not changed. If you have BTI steps in your production JCL that reference a job with a new name, you must change the production JCL to reflect the new job name.