> 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. Fred! ----------------------------------------------------------------- ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. ----------------------------------------------------------------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
