Find 'em, Fix 'em / Investigation and Planning /Plan!Plan!Plan!/Applications

### What about CICS?

We strongly recommend that you migrate to CICS/ESA® 4.1, which uses both two-digit and four-digit year format. CICS V3.3 and earlier will not run across midnight 12/31/1999, although you might be able to do a complete cold rebuild/restart for V3.3. For the full details, including limitations when using prior releases, see CICS/ESA 4.1 Support for Year 2000 and VSE and Year 2000 -- CICS/VSE® support .

#### CICS COBOL

CICS V4 supports OS/VS COBOL, so your CICS COBOL programs can migrate to a new run-time, just as has been recommended for batch COBOL programs. For example, if your CICS V1/2/3 COBOL module includes OS/VS COBOL modules and CICS modules, run-time migration for OS/VS COBOL will require re-linking to replace the OS/VS COBOL runtime routines with Language Environment run-time routines. A re-link is not required to obtain the CICS V4 modules

A re-link is required for your NORES cases to replace your old library routines. The only CICS routine is the command level support stub. It does not need to be replaced.

Note: A relink is not required to run with Language Environment; it is required only to ensure that you are using supported versions of the library routines. For the RES cases, just replace the OS/VS COBOL library with Language Environment library.

#### Language Environment

In OS/390 Language Environment Installation and Customization there are about three pages of instructions of how to make Language Environment available to your CICS programs.

#### CICS PL/I

CICS V4 supports OS/PL/I, so your CICS PL/I programs can migrate to a new run-time, just as has been recommended for batch PL/I programs. For example, if your CICS V1/2/3 PL/Imodule includes OS PL/I modules and CICS modules, run-time migration for OS PL/I will require re-linking to replace the OS PL/I runtime routines with Language Environment run-time routines. A re-link is not required to obtain the CICS V4 modules