That would mean that all functions must be updated to use PDSE datasets rather than PDS for Cobol Compile and Load libraries.
If that is correct, that will be a large change to a lot of processes in a lot of shops. I know I can use IEBCOPY to copy my current PDS loadlib to a PDSE library and then I would be good to go. However the changes to my JCL is another matter. I will most likely need to change out all of my current Load libraries in CICS, IMS, MQ, DB2, Prod batch to the new PDSE library in order to move into position for Cobol V5. Please let me know if I am mis-understanding. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Ross Sent: Saturday, September 07, 2013 9:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 2.1 and tools like COBOL 5.1, Fault Analyzer, Debug Tool, etc >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. No, the COBOL Migration Guide is correct, all COBOL programs produce GOFF output with COBOL V5, so after Binding you will have a program object and it must reside in a PDSE. I thought it was pretty clear myself, any suggestions for how we could have made it clearer? Cheers, TomR >> COBOL is the Language of the Future! << ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
