For the latest information on upgrading to and from any versions of CICS TS, see CICS TS V5.6.

Upgrading CICS Transaction Server

To upgrade your CICS regions to CICS® Transaction Server for z/OS®, Version 5 Release 2, carry out the tasks described here. There are some general upgrading tasks which you must always perform. There are also upgrading tasks for some specific functional areas where there is a need for special considerations.

Subtopics

Upgrade procedures for all CICS regions
Complete these tasks when you upgrade any CICS Transaction Server region to CICS Transaction Server for z/OS, Version 5 Release 2.
Upgrading application programs
CICS translator support for pre-Language Environment compilers is withdrawn. Runtime support is provided for existing application programs that were developed using these compilers, except for OS/VS COBOL and OO COBOL programs, which do not have runtime support.
Upgrading Business Transaction Services (BTS)
When you upgrade your BTS environment to CICS Transaction Server for z/OS, Version 5 Release 2, you might need to migrate the DFHLRQ data set. Be aware that even if you are not explicitly making use of BTS services in your applications, it is possible that they are being exploited by vendor code or IBM-supplied products executing within your CICS environment.
Communicating over IPIC with different levels of CICS
If both an APPC or MRO connection and an IPIC connection exist between two CICS regions, and both have the same name, the IPIC connection takes precedence. However, if your terminal-owning region (TOR) and application-owning region (AOR) are in CICS systems that are using different levels of CICS, the rules can differ.
Upgrading multiregion operation (MRO)
To upgrade CICS multiregion operation (MRO) support, install the latest DFHIRP and DFHCSVC modules in the MVS™ link pack area (LPA) and carry out tests.
Upgrading the Java environment
When you upgrade to a new CICS release, you might require changes to your JVM profiles and to other aspects of your Java™ environment. You might also require changes to your Java applications.
Upgrading the CICS-WebSphere MQ connection
If you use the CICS-WebSphere MQ adapter, bridge, trigger monitor, or API crossing exit to connect CICS to WebSphere® MQ, check your configuration and make any necessary changes.
Upgrading the CICS DB2 connection
This information enables you to plan and carry out installation or upgrade procedures in the CICS DB2® environment.
Upgrading SOAP web services
If you have used SOAP web services in earlier CICS releases, be aware of the following changes when you upgrade to CICS Transaction Server for z/OS, Version 5 Release 2.
Upgrading JSON web services
If you used JSON web services in earlier releases, be aware of the following changes when you upgrade to CICS Transaction Server for z/OS, Version 5 Release 2.
Upgrading SAML support
If you used Security Assertion Markup Language (SAML) support in earlier CICS releases, follow this procedure to upgrade to CICS Transaction Server for z/OS, Version 5 Release 2.
Upgrading platforms, applications, policies, and CICS bundles
If you have used platforms, applications, policies, and CICS bundles in CICS in earlier releases, be aware of the following changes when you upgrade to CICS Transaction Server for z/OS, Version 5 Release 2.

Parent topic: Upgrading from Version 4 Release 2

dfhe5_planning.html | Timestamp icon

Last updated: Saturday, 15 June 2019