On the other hand, don't do it like I've sorta been forced to do. Due to lack of resources to test new COBOL releases, I've been carrying forward the release I installed somewhere around a/OS 1.4 :(
And, with one of those replace the systems with an ERP sometime in the next decade coming on, plus budget cuts, we have even less development staff and less incentive to get the compiler current. Cobol has not been a major language for us in sometime. Most code is in Natural. Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Shane > Sent: Wednesday, June 24, 2009 2:04 AM > To: [email protected] > Subject: Re: Enterprise COBOL for z/OS V4 > > On Tue, 2009-06-23 at 17:17 -0700, Skip Robinson wrote: > > > I'm a little concerned about this transition phase in which > application > > folks implicitly use the new compiler but 'move' load modules to the > old LE > > environment. > > I'm a bit with Ted on this - you need to "fix" the process Skip. > After a (very) bad experience with some LE maint a few years back, our > major customer at the time mandated that *no* in-house promotions would > occur whilst a resvol was being rolled out. > In the rare need for an actual implementation direct into prod, there > were emergency procedures to get the work done in that environment. > Needed a *real* good justification - didn't get authorized too often. > > Shane ... > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
