Don't know for COBOL, but we have some experience with PL/1 here, and as long as you don't use some of the fancier new options like RENT, DLL etc., you don't need your output libraries to be PDSEs, because the resulting load objects don't have the properties that need them to be GOFFs or program objects type 3 (PO3) - I guess, that's the difference.
The Binder, AFAIK, does output into normal PDS libraries as well. But it will refuse to do so if the load objects need to be PO3 or GOFF. So I guess you have to check if you need the new options or if you can live without them. At our site, for example, we decided to stay with NORENT - our modules are all naturally reentrant - and we build classical load modules (which are limited to 16 MB in size, BTW), and so we still use normal PDS libraries. But there is a neighbor site in the same company, where all is PDSE - because of compiler options DLL and RENT. Kind regards Bernd Am 06.09.2013 14:01, schrieb Jousma, David:
A quick look in the ENT COB 5.1 migration guide does turn up this jewel... Binding (link-editing) Enterprise COBOL programs What is the difference between an object module, a load module, and a program object? An object module is the output of the compiler and input to the binder. A load module is a non-GOFF executable that is output from the binder with an Enterprise COBOL V4.2 object module. A program object is a new style GOOF executable that is the output from the binder when binding an object module from Enterprise COBOL V5.1. Are PDS and PDSE data sets allowed for object and load modules with Enterprise COBOL V5? Compiler output data sets can be PDS or PDSE, including the object module. The output of the bind step must be a PDSE. When COBOL object modules are linked (bound) they become program objects and must be stored in PDSE data sets. This is going to be a big undertaking for us. We have hundreds of application load libraries that are PDS, NOT PDSE. _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
