On Wed, 29 Jul 2015 06:17:31 -0700, Charles Mills wrote: >In a large shop the old PDS would be in continuous use and therefore >difficult to swap out. > A shop must be prepared to do this in the event of hardware replacement.
This sounds like a good argument for a facility to rename a data set while in use. Copy PDS to PDSE and swap the names. I know it wouldn't be easy, but I'm too familiar with the facility in UNIX not to recognize its value or to deem it worthless. >-----Original Message----- >From: Fred van der Windt >Sent: Tuesday, July 28, 2015 10:40 PM >> >> ... The customer >> presumably has thousands of jobs that say //STEPLIB DD DSN=OLD.PDS and no > > manpower to change them all. This would let them catalog COBOL 5 programs >in NEW.PDSE and have it be automagically searched first whenever the JCL >said DSN=OLD.PDS. >> >> Charles > >Why would that require JCL changes? You could just replace OLD.PDS by a >PDSE. ... > What are the possible technical obstacles? o Are there any load modules that simply can't be converted to program objects? o Might a customer have a RECFM=U PDS that contains both load modules and non-program data objects? A better solution might be to extend the capability of PDSE, allowing a mixture of program objects and non-program objects. I know it might not be easy, but the restriction should never have been established in the first place. Or, I could envision a dual-fork scheme where a single catalogued DSN identifies both a PDS and a PDSE, but with no overlap in member names permitted. That would eliminate the auditing hazard. When an auditing process scans JCL to find all references to a DSN, should it automatically report both the PDS and the PDSE branches with the coming z/OS 2.2 facility? It would be valuable if: o That facility prohibits overlapping member names. o Facilities such as ISPF DDLIST correctly report members in either branch. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
