Migrating to CICS Transaction Server 2.2: User Experience - Summary
-
CICS TS 2.2 was the "quickest/cleanest" install I've been involved
with. We've had ~100% (aka "five nines" or 99.999%) scheduled
availability of our production CICS environment since this conversion.
-
With ~10K CICS application programs at our site, only 3 had
to be modified for this conversion.
-
Our migration was aided by the fact that we're currently a
"Classic CICS" site. We're glad that IBM continues to enhance
"Classic CICS" and extend the product fuctionality.
-
MVS logger required more research, planning, resources, and implementation work
than we would have liked. (Potential candidate for the "understatement
of the year" ;-).
-
OEM/ISV CICS ancillary product support was a typical migration inhibitor,
with the notable exception of !CANDLE Omegamon II for CICS V520. We've
been unable to do thorough "threadsafe" testing in CICS TS 2.2
due to problems we've had with CA-InterTest 6.1 for CICS.
-
CICS is and has been a stable and robust server for us - plans
are to continue to exploit CICS, the CICS Socket Interface, and
some of the newer CICS functionality to provide even more CICS
services at our site.
Display the Summary Notes, or
Jump to Appendix, or
Jump to Table of Contents.
The URL for this document is
<http://nersp.nerdc.ufl.edu/~sfware/share100/summary.html>.
Last updated on February 6, 2003, by
Steve Ware,
<mailto:sfw@nersp.nerdc.ufl.edu>.
Page 58 of 60