Yes, you can use the Endevor Batch administration for this. Search Techdocs for "Manage Environments in Batch".
The output from this process can be tailored and then used as input. However, I recommend you start with a small sample. I seem to remember that you might get errors for attempting to MOVE elements after their Generate processor name has changed.
A more surgical alternative is the use of the CSV utility and the Table tool. This approach also leverages the Endevor Batch administration facility but can target just the specific area(s) you want to change. In a single job, you can execute the CSV utility to list the processor groups you want to change. Then a Table tool step could include something like this:
//MODEL DD *
*Update Gen processor at &PROC_GRP_NAME &SYS_NAME &TYPE_NAME &STG_#
* previously updated on &UPDT_DATE &UPDT_TIME by &UPDT_USRID
DEFINE PROCESSOR GROUP '&PROC_GRP_NAME'
TO ENVIRONMENT &ENV_NAME
SYSTEM &SYS_NAME
TYPE &TYPE_NAME
STAGE NUMBER &STG_#
GENERATE PROCESSOR NAME IS 'GENB'
DO NOT ALLOW FOREGROUND EXECUTION
.
//OPTIONS DD *
If PROC_TYPE /= 'GEN' then $SkipRow = 'Y'
if SYM_OVRD_# > '1' then $SkipRow = 'Y'
You can review the results before making the output from this job be input to a Batch Administration job.
Original Message:
Sent: 10-06-2021 05:42 PM
From: Herbert Bustos
Subject: Mass update to Endevor Generate Processor names across all the System Environment.
Hello,
We are looking for a solution to do a mass update rename Generate Processor names across all the System Environments.
Example. Rename Generate processor "GENA" to Generate processor "GENB". Is there a known solution to this, perhaps a Batch job? We are running on Version 18.0.12. Any information on this is very much appreciated.