When we went from CICS 4.1 + COBOL/2 to CICS 4.1 + LE, we switched to the LE run time libraries with absolutely no difficulty. We did have some OS/VS COBOL that posed some problems, but we took that opportunity to upgrade the application code rather than try to make it work. Migrating to the new compiler was a little more fun. Most of the Plain Jane COBOL/2 source worked just fine. However, we are still uncovering the occasional "poor" programming practice under COBOL/2 that is no longer acceptable with COBOL/MVS. I am just now installing CICS/TS 1.3 so I can't offer any input there, although I am not anticipating any great difficulty migrating our current applications. Unless this application is doing something "out in the weeds" it should work. I don't know that I'd stake my professional reputation on "should work" as opposed to actually getting it tested under your proposed configuration.

Regards,

Donald A. Grinsell CICS Systems Programmer State of Montana

-----Original Message----- From: Fred Hoffman [mailto:fhoffman@TAD.ORG] Sent: Thursday, June 15, 2000 3:07 PM To: CICS-L@LISTSERV.UGA.EDU Subject: Re: Version/Release Concerns

FWIW, I basically asked the same question early last week. I was told that when that site went to CICS TS, the applications were not re-compiled and they seemed to work alright. My situation is similar, however, the language PL/I using the LE runtime libraries. I thought I read something in the migration manual that sorta said that if you were using LE, the modules should be upward compatible. FWIW.

-----Original Message----- From: WOB [mailto:wobconsult@SPRYNET.COM] Sent: Thursday, June 15, 2000 4:01 PM To: CICS-L@LISTSERV.UGA.EDU Subject: Version/Release Concerns

I've got a situation that I need to put to bed. We will be installing a Credit Card System in October that has not been tested in a TS environment and this has me concerned. Additionally, it has NOT been tested in COBOL/MVS environment. Just COBOL2, Release 4.0, which also has me a bit worried. <snip> WOB