On 7/29/2015 1:40 AM, Fred van der Windt wrote:
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!
Fred,
Just one problem with your implementation plan. Most sites I know would
not want to recompile every COBOL program they run into a PDSE, then do
a rename swap to implement. IEFOPZxx is great solution to this problem.
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
