Hi Ronald,
Can I first ask how many processors we are talking about. If it's only a few, then using cut-n-paste to capture the listings from the Processor Group Panel (option "L") sounds like the quickest/easiest solution.
But two other options sprint to mind:
a) Build a batch job that performs generates/moves/deletes for each processor/processor group combination and save the listings - this would capture not only the processor listing but also a trail of symbol substitutions which I'd argue is almost as important. or...
b) Set up a new (or temporary) admin system and transfer bypass delete all your processors and generate them with listings at the new location. Yes, they would pick up the newest versions of any copybooks but I'd argue that KNOWING what you have is probably more valuable than trying to chase down prior levels of the copybooks.
If retaining the absolute version of the include members is important, you could use the last generate date of the processor with the component information to identify the relevant version of the include members and transfer
that specific version of the include member, and then do the generate of the processor. If you worked through your processors in generate date order (earliest to newest) you'd end up with a duplicate of your production environment and all the listings would be accurate - You could even swap over to this new system and archive the old one safely.
One last thought - if you make the new listing library a PDS/E version2, and enable generations, you could use these generations as a way to review compare listings with old/new include members. Or of course you could just check them into Endevor.
------------------------------
Sr Principal Software Engineer
------------------------------
Original Message:
Sent: 05-28-2020 11:44 AM
From: Ronald O'Loughlin
Subject: a batch option to extract processor listings from the processor load
My site never created processor listings libraries. So over time (years) any processors generated (ADD/UPDATE/GENERATE/MOVE) listings have not captured since the beginning. However one can go to a processor group panel and use the L option and see the listing of the processor as it was last generated. One of the other variables is that we use ++INCLUDES to bring in common JCL code into a processor(s). So regenerating a processor is not desirable since we want to see the processor that is being used since it was last generated. Finally we are reviewing a large number of processors.
So what we would like to have is a 'batch' process that acts like the processor group panel L option. So the batch job would go through all the members of the processor load and de-assemble the loads to create the listing. Which I was told that is what the L option is doing. So all the listings are created. Which would then be put into a processor listing library to create the base. Case#31932500 was opened and closed.
------------------------------
Endevor Admin
SSA
------------------------------