In a large shop the old PDS would be in continuous use and therefore difficult to swap out.
I agree with the people who say this is a recipe for confusion but I certainly understand IBM's thinking also. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Fred van der Windt Sent: Tuesday, July 28, 2015 10:40 PM To: [email protected] Subject: Re: z/OS 2.2 announcement > This was discussed at the vendor TDM but I think I am not talking out of school here now that this is announced ... > > One obstacle to customers converting to COBOL 5 is the requirement > that the resulting executable programs reside in a PDSE. 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. > > AFAIR ... > > Charles Why would that require JCL changes? You could just replace OLD.PDS by a PDSE. I will admit that 'OLD.PDS' is a silly name for a PDSE but adding a .PDS suffix to a PDS seems silly to begin with. But is is an easy fix. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
