>If you set up new PDS/E program libraries for only V5 program code, then >any time maintenance on a COBOL program is done the maintainer must be >aware whether this is the first time this program has compiled with V5 >and if so, be sure any related production JCL gets changed to reference >the new library in sync with the program installation and be sure the >obsolete load module in some PDS gets purged at the same time to prevent >possible execution of obsolete code.
How about if shops start changing COBOL build processes today to use PDSE datasets for COBOL V4 (or COBOL 3) programs? Step 1 would be to allocate new PDSE datasets for each zone of load libraries Step 2 would be to add the new PDSE dataset(s) to load library concatenations where needed. If put first it would guarantee access to new programs. Step 3 would be to change build processes to link old COBOL programs into PDSEs. Step 4 would be to make sure this works for all systems and that old (unreachable) programs get deleted from PDS datasets Step 5 from time to time, move needed load modules from PDSs to PDSEs until all are moved. Step 6 when all code has been moved, the only programs in PDS should be unused, and the PDS datasets could be deleted If this plan was used, the COBOL V5 PDSE requirement would not be disruptive. My question, is it do-able? Cheers, TomR >> COBOL is the Language of the Future! << ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
