Any difference should be documented in the migration guides I would think. On Tue, Jan 14, 2020 at 1:38 PM Frank Swarbrick <frank.swarbr...@outlook.com> wrote:
> I understand that the runtime is part of LE, and is generally shared > between versions (at least V5 and V6 seem to share the same runtime for > many/most functions). Conceivably it's still possible that the code > generated by a certain version of a compiler may have defects. Probably > less likely if the code is in a pre-existing feature. > > My question has to do with the (probably slight) possibility that the code > generated by one compiler would be different, for the same statement, for > another. > > ________________________________ > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf > of Charles Mills <charl...@mcn.org> > Sent: Monday, January 13, 2020 4:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU> > Subject: Re: Migrating to new compiler release > > Caution and backups and fallback strategies are always good, but I don't > think there is much relationship between *running* a COBOL version X > program > and having the *compiler* version Y installed. I believe all of the runtime > is part of LE, not the compiler, and compatibility from VS COBOL II (if I > recall correctly) to current C++, PL/I and COBOL is what LE does for a > living. Not always perfectly, but that is what APARs and PTFs are for. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Frank Swarbrick > Sent: Monday, January 13, 2020 3:33 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Migrating to new compiler release > > I was wondering what "methodologies" shops have for migrating to a new > "release" within the same "version" of a compiler. Specifically, we > currently have Enterprise COBOL 6.2 (V6 R2) and 6.3 is now available. Our > systems group asked if we just wanted to "replace" 6.2 with 6.3. I'm a bit > wary especially of a program having been compiled with V6.2 but then > implemented with V6.3. Am I over thinking this, perhaps because of the > large difference in the compiler from V4 to V5? What is the likelihood of > a > compiler bug being introduced in V6.3 for code that worked in V6.2? > Perhaps > very, very little. But I'd still like to hear thoughts and opinions. > > For what its worth, along with 6.2 we still have 4.2 and 5.2 installed. > But > we really should only be using 6.2 at this point any time a program is > recompiled. Anyway, up to this point we've always made sure that the > production compile is done with the same version/release as all of the > testing. > > Thanks, > Frank > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
