I opted to create a complete second set of new generate processors and processor groups with consistently similar names to the originals. There is no extra cost for keeping the version 4 compiler, so I installed version 6.2 to a different load library and the COBOL compile step has a steplib to that new library in the new processors. I hardcode the non-default compile options that vary by stage in the new processors, such as TEST/NOTEST, PARMCHECK, SSRANGE, INITCHECK. I generated everything in an environment created solely for this purpose. I am now moving everything to the next stage. I will then search the listings for the INITCHECK warning message and notify the developers if it is found for any of their programs.
I will then define the new processor goups so that the developers will be able to choose which processor group that they use. We may send them a warning message each time they generate with an version 4 processor group. We will ask the developers to generate all of their cobol programs with the new processor groups, execute the generated program, look for the run time warning messages, and modify their code to eliminate the run time warning messages when any are found.