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 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Frank Swarbrick Sent: Tuesday, July 28, 2015 1:28 PM To: [email protected] Subject: Re: z/OS 2.2 announcement I found this to be interesting, but I don't quite understand it: "z/OS V2.2 is designed to support a new IEFOPZxx parmlib member in which you can specify pairs of partitioned (PDS and PDSE) data sets. In each pair, you can specify one that is to be searched ahead of its counterpart data set when programs are fetched. This new function is intended to allow you to insert program libraries ahead of others in the link list, in STEPLIB and JOBLIB concatenations, and for LLA-managed libraries without making JCL changes. A new DISPLAY IEFOPZ command is designed to display information about existing pair definitions, and a SET IEFOPZ command is designed to allow you to add, remove, or change pair definitions dynamically. This is expected to be useful for activities such as converting application program libraries from PDS to PDSE, as is necessary for converting to COBOL V5 (5655-W32), without requiring JCL changes. Availability of these functions is planned for December 2015 with the PTF for APAR OA47689." Can someone "in the know" give an example of how this would work with JOBLIB or STEPLIB? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
