Re: Enterprise COBOL version runtime
Hi, Sorry I should have been clearer - yes the C/C++ prelinker. thanks, Simon -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: 03 November 2017 16:39 To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Enterprise COBOL version runtime WARNING: this email has originated from outside of the SSE Group. Please treat any links or attachments with caution. ** Never mind my dumb question. I just realized you are talking about the C/C++ pre-linker, not the CICS and DB2 source code pre-processors. Apologies for wasting bandwidth. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Friday, November 03, 2017 12:33 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Enterprise COBOL version runtime Simon, We are transitioning to COBOL V5.2 from V4.2 and have been compiling with both the CICS pre-linker and the DB2 pre-linker with no trouble so far. Well, a little trouble with the DB2 pre-linker, you do have to resolve all COPY statements before you feed source to the DB2 pre-linker, but the COBOL V5.2 MDECK(NOCOMPILE) option makes that easy. Can you describe the compile failures in a little more detail please? Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wheeler, Simon Sent: Friday, November 03, 2017 12:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Enterprise COBOL version runtime Hi, We hit a problem relating to the pre-linker. COBOL v4 is the last release of COBOL to support calls to subroutines/sub-programs that have used the pre-linker. We have an application written in C and COBOL that extensively used the pre-linker. During the COBOL upgrade we discovered that compiles were failing. Consequence was that we had to regress the COBOL upgrade! Still working on the upgrade plan to COBOL v6. thanks, Simon Wheeler -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: 02 November 2017 12:02 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Enterprise COBOL version runtime ** First off, why go to V5, when V6.2 is now out.In order for both compilers to co-exist, you will have to have different Dataset names for the compiler. Also, make sure that all the LE support maintenance for the newer version is installed and active on all of your systems. Lastly, you probably know, but the load libraries need to be PDSE, and new cobol wont co-exist in the same run-unit with OSVS COBOL compiled modules, so you could have some unintended problems if modules shared get upgraded that also include calls to other older modules. There is an entire migration guide discussing all of this. We are just starting down this path too. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, November 02, 2017 7:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Enterprise COBOL version runtime **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello fellow dragon-slayers! We are finally biting the bullet and getting ready to move forward with the Enterprise Cobol v 5. I know there are a lot of changes to v 5 from the world as we know it, and I will be perusing the documentation very soon, but can someone give me a quick 3-foot view of this upgrade specific to one question? If we implement v 5 in our development LPAR before our production LPAR, can we run the v 5 programs/load modules in our v4 production system? Are there any cross-version things we need to be aware of? Thanks for helping me with this question (my management would thank you, too!). Billy -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu
Re: Enterprise COBOL version runtime
Simon, We are transitioning to COBOL V5.2 from V4.2 and have been compiling with both the CICS pre-linker and the DB2 pre-linker with no trouble so far. Well, a little trouble with the DB2 pre-linker, you do have to resolve all COPY statements before you feed source to the DB2 pre-linker, but the COBOL V5.2 MDECK(NOCOMPILE) option makes that easy. Can you describe the compile failures in a little more detail please? Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wheeler, Simon Sent: Friday, November 03, 2017 12:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Enterprise COBOL version runtime Hi, We hit a problem relating to the pre-linker. COBOL v4 is the last release of COBOL to support calls to subroutines/sub-programs that have used the pre-linker. We have an application written in C and COBOL that extensively used the pre-linker. During the COBOL upgrade we discovered that compiles were failing. Consequence was that we had to regress the COBOL upgrade! Still working on the upgrade plan to COBOL v6. thanks, Simon Wheeler -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: 02 November 2017 12:02 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Enterprise COBOL version runtime ** First off, why go to V5, when V6.2 is now out.In order for both compilers to co-exist, you will have to have different Dataset names for the compiler. Also, make sure that all the LE support maintenance for the newer version is installed and active on all of your systems. Lastly, you probably know, but the load libraries need to be PDSE, and new cobol wont co-exist in the same run-unit with OSVS COBOL compiled modules, so you could have some unintended problems if modules shared get upgraded that also include calls to other older modules. There is an entire migration guide discussing all of this. We are just starting down this path too. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, November 02, 2017 7:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Enterprise COBOL version runtime **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello fellow dragon-slayers! We are finally biting the bullet and getting ready to move forward with the Enterprise Cobol v 5. I know there are a lot of changes to v 5 from the world as we know it, and I will be perusing the documentation very soon, but can someone give me a quick 3-foot view of this upgrade specific to one question? If we implement v 5 in our development LPAR before our production LPAR, can we run the v 5 programs/load modules in our v4 production system? Are there any cross-version things we need to be aware of? Thanks for helping me with this question (my management would thank you, too!). Billy -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Enterprise COBOL version runtime
Hi, We hit a problem relating to the pre-linker. COBOL v4 is the last release of COBOL to support calls to subroutines/sub-programs that have used the pre-linker. We have an application written in C and COBOL that extensively used the pre-linker. During the COBOL upgrade we discovered that compiles were failing. Consequence was that we had to regress the COBOL upgrade! Still working on the upgrade plan to COBOL v6. thanks, Simon Wheeler -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: 02 November 2017 12:02 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Enterprise COBOL version runtime ** First off, why go to V5, when V6.2 is now out.In order for both compilers to co-exist, you will have to have different Dataset names for the compiler. Also, make sure that all the LE support maintenance for the newer version is installed and active on all of your systems. Lastly, you probably know, but the load libraries need to be PDSE, and new cobol wont co-exist in the same run-unit with OSVS COBOL compiled modules, so you could have some unintended problems if modules shared get upgraded that also include calls to other older modules. There is an entire migration guide discussing all of this. We are just starting down this path too. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, November 02, 2017 7:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Enterprise COBOL version runtime **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello fellow dragon-slayers! We are finally biting the bullet and getting ready to move forward with the Enterprise Cobol v 5. I know there are a lot of changes to v 5 from the world as we know it, and I will be perusing the documentation very soon, but can someone give me a quick 3-foot view of this upgrade specific to one question? If we implement v 5 in our development LPAR before our production LPAR, can we run the v 5 programs/load modules in our v4 production system? Are there any cross-version things we need to be aware of? Thanks for helping me with this question (my management would thank you, too!). Billy -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of the SSE Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Unless specifically stated otherwise, this email (or any attachments to it) is not an offer capable of acceptance or acceptance of an offer and it does not form part of a binding contractual agreement. SSE plc Registered Office: Inveralmond House 200 Dunkeld Road Perth PH1 3AQ Registered in Scotland No. SC117119 Authorised and regulated by the Financial Conduct Authority for certain consumer credit activities. www.sse.com ** -- For IBM-MAIN subscribe
Re: Enterprise COBOL version runtime
If you are at z/OS V2.2 or above look at parm member IEFOPZxx - this allows you to setup a PDSE to be searched in front of a PDS. This is handy if you do not want to convert all JCL to use the PDSE for COBOL required loadlibs Also run FIXCAT process for all IBM and OEM products to verify you have all maintenance on for COBOL compiler you are going to You should roll out any fixes you do not currently have on first, then upgrade the compiler. https://www-03.ibm.com/systems/z/os/zos/features/smpe/fix-category.html For example SET BDY(GLOBAL). REPORT MISSINGFIX ZONES(ZOSR21T) FIXCAT(IBM.Coexistence.z/OS.V2R3). Specific to COBOL IBM.TargetSystem-RequiredService.Enterprise-COBOL.V5R1Fixes required on other IBM products to support the Enterprise COBOL for z/OS V5.1 compiler and programs compiled with it. IBM.TargetSystem-RequiredService.Enterprise-COBOL.V5R2Fixes required on other IBM products to support the Enterprise COBOL for z/OS V5.2 compiler and programs compiled with it. IBM.TargetSystem-RequiredService.Enterprise-COBOL.V6R1Fixes required on other IBM products to support the Enterprise COBOL for z/OS V6.1 compiler and programs compiled with it. IBM.TargetSystem-RequiredService.Enterprise-COBOL.V6R2Fixes required on other IBM products to support the Enterprise COBOL for z/OS V6.2 compiler and programs compiled with it. Vendors like CA also have fixcat categories for IBM software requirements Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of ??? ?? ??? > Sent: Thursday, November 02, 2017 5:10 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Enterprise COBOL version runtime > > I'm sure you've seen this but compile time and compile memory usage are > significantly higher. > We've seen compile time 50 times higher that with older version of the > compiler. > With v6.1 we actually run out of auxiliary storage when compiling a very > large program. > > Gadi > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Bill Ashton > Sent: Thursday, November 2, 2017 1:58 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Enterprise COBOL version runtime > > Hello fellow dragon-slayers! > > We are finally biting the bullet and getting ready to move forward with the > Enterprise Cobol v 5. I know there are a lot of changes to v 5 from the world > as we know it, and I will be perusing the documentation very soon, but can > someone give me a quick 3-foot view of this upgrade specific to one > question? > > If we implement v 5 in our development LPAR before our production LPAR, can > we run the v 5 programs/load modules in our v4 production system? Are there > any cross-version things we need to be aware of? > > Thanks for helping me with this question (my management would thank you, > too!). > > Billy > > -- > Thank you and best regards, > *Billy Ashton* > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Enterprise COBOL version runtime
I'm sure you've seen this but compile time and compile memory usage are significantly higher. We've seen compile time 50 times higher that with older version of the compiler. With v6.1 we actually run out of auxiliary storage when compiling a very large program. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, November 2, 2017 1:58 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Enterprise COBOL version runtime Hello fellow dragon-slayers! We are finally biting the bullet and getting ready to move forward with the Enterprise Cobol v 5. I know there are a lot of changes to v 5 from the world as we know it, and I will be perusing the documentation very soon, but can someone give me a quick 3-foot view of this upgrade specific to one question? If we implement v 5 in our development LPAR before our production LPAR, can we run the v 5 programs/load modules in our v4 production system? Are there any cross-version things we need to be aware of? Thanks for helping me with this question (my management would thank you, too!). Billy -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN לתשומת ליבך, בהתאם לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה שלה (להלן : "החברה") וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance with Malam and/or its subsidiaries (hereinafter : "Malam") regulations and signatory rights, no offer, agreement, concession or representation is binding on the Malam, unless accompanied by a duly signed separate document (or a scanned version thereof), affixed with the Malam seal. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Enterprise COBOL version runtime
First off, why go to V5, when V6.2 is now out.In order for both compilers to co-exist, you will have to have different Dataset names for the compiler. Also, make sure that all the LE support maintenance for the newer version is installed and active on all of your systems. Lastly, you probably know, but the load libraries need to be PDSE, and new cobol wont co-exist in the same run-unit with OSVS COBOL compiled modules, so you could have some unintended problems if modules shared get upgraded that also include calls to other older modules. There is an entire migration guide discussing all of this. We are just starting down this path too. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Thursday, November 02, 2017 7:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Enterprise COBOL version runtime **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello fellow dragon-slayers! We are finally biting the bullet and getting ready to move forward with the Enterprise Cobol v 5. I know there are a lot of changes to v 5 from the world as we know it, and I will be perusing the documentation very soon, but can someone give me a quick 3-foot view of this upgrade specific to one question? If we implement v 5 in our development LPAR before our production LPAR, can we run the v 5 programs/load modules in our v4 production system? Are there any cross-version things we need to be aware of? Thanks for helping me with this question (my management would thank you, too!). Billy -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Enterprise COBOL version runtime
Hello fellow dragon-slayers! We are finally biting the bullet and getting ready to move forward with the Enterprise Cobol v 5. I know there are a lot of changes to v 5 from the world as we know it, and I will be perusing the documentation very soon, but can someone give me a quick 3-foot view of this upgrade specific to one question? If we implement v 5 in our development LPAR before our production LPAR, can we run the v 5 programs/load modules in our v4 production system? Are there any cross-version things we need to be aware of? Thanks for helping me with this question (my management would thank you, too!). Billy -- Thank you and best regards, *Billy Ashton* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
