I should have also included this section GOFF stands for Generalized Object File Format . It is an enhanced type of object module introduced by the binder in DFSMS/MVS 1.3 and produced by the High Level Assembler, COBOL, and C++. GOFF supports long names and multipart modules, and provides some other new features. These object modules can be stored as sequential files, as members of PDS or PDSE libraries, or as z/OS UNIX file system files.
So unless the new stuff is used, you may be okay Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Friday, September 06, 2013 5:34 AM To: [email protected] Subject: Re: z/OS 2.1 and tools like COBOL 5.1, Fault Analyzer, Debug Tool, etc. Dave, I think this redbook may help http://www.redbooks.ibm.com/redbooks/pdfs/sg246106.pdf The binder supports a modified extended object module, produced by the C and C++ compilers, and an entirely new object module format, called GOFF. This new object module type is described in 7.2.5, GOFF If I am reading this correctly, the BINDER would need to use a PDSE output file if there is JAVA, C/C++ type of programs. If you have native cobol, then you might be able to continue the LKED with BINDER to a non PDSE. So any process currently using BINDER for JAVA or C/C++ would most likely already be using a PDSE for the program object output. It might be possible that IBM did not document that section clearly enough (big surprise ) That is just a guess. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Friday, September 06, 2013 5:01 AM To: [email protected] Subject: Re: z/OS 2.1 and tools like COBOL 5.1, Fault Analyzer, Debug Tool, etc. 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 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Friday, September 06, 2013 7:36 AM To: [email protected] Subject: Re: z/OS 2.1 and tools like COBOL 5.1, Fault Analyzer, Debug Tool, etc. I'm curious about your statement: "With COBOL 5.1, AFAIK, comes also the requirement of the loadlibraries to be PDSE. Which we DON'T have today, neither in production or test systems." If you mean the product code comes in PDSE's then that's no big deal. But if you are saying the output of the compiler has to be PDSE's, in other words, all application load libraries have to be PDSE's then I am concerned. _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected]<mailto:[email protected]> 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Thomas Berg Sent: Friday, September 06, 2013 5:54 AM To: [email protected]<mailto:[email protected]> Subject: z/OS 2.1 and tools like COBOL 5.1, Fault Analyzer, Debug Tool, etc. We are going to eventually install 2.1 in the future. Besides the OS we have to decide how handle the new COBOL 5.1 and it's dependencies towards Fault Analyzer, Debug Tool and other productivity tools. E g which version/release is required for a certain product to work with another product. And can we upgrade to the latest version of e g Fault Analyzer (that otherwise comes with 2.1) at our z/OS 1.13 and get it working ? As a way to take possible problems in advance of the install of 2.1. With COBOL 5.1, AFAIK, comes also the requirement of the loadlibraries to be PDSE. Which we DON'T have today, neither in production or test systems. Do anyone have experiences of these (potential) problems ? Can you let me take part of them I would be grateful! I understand that some at this list have installed and run z/OS 2.1, but have you used COBOL or the other tools ? Med Vänlig Hälsning Thomas Berg ___________________________________________________________________ Thomas Berg Specialist zOS\RQM\IT Delivery SWEDBANK AB (Publ) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
