Migrating to the latest DFHIRP

The CICS® TS for z/OS®, Version 3.1 DFHIRP module is compatible with earlier releases, and is designed to work with all releases of CICS.

The following steps are a guide to migrating to MRO, with the latest DFHIRP and DFHCSVC modules installed in the MVS™ link pack area (LPA). For information about how to perform some of these steps, such as installing the SVC or IRP modules in the LPA, see the CICS Transaction Server for z/OS Installation Guide. Note that these steps assume that RACF®® is your external security manager (ESM).

1. Install the CICS SVC
Install the CICS TS SVC routine, DFHCSVC, in the LPA, and specify a new CICS SVC number for this routine in the MVS SVCPARM table. (If the new DFHCSVC has to coexist with an older version, rename one of them so that both versions can be installed in the LPA. However, this is not recommended or necessary: DFHCSVC is compatible with earlier releases and the latest CICS TS version supports all the earlier releases of CICS.)
2. Test the CICS SVC
Test the new SVC on CICS TS stand-alone regions, without using any MRO. You can do this running the CICS IVP, DFHIVPOL.
3. Install the IRP
Install the CICS TS interregion communication program, DFHIRP, in a suitable LPA library, and IPL MVS (with the CLPA option).

Start of changeDo not use the dynamic LPA function to replace DFHIRP for migration between releases, as this can cause incompatibility between control blocks, resulting in abend situations.End of change

4. Test current production release
Test your production MRO CICS regions, under your existing release of CICS, but using the new SVC number and the new DFHIRP. For this test, run without any logon or bind-time security checking--that is, do not define any RACF FACILITY class profiles.
5. Define RACF FACILITY resource class profiles
Define the required DFHAPPL.applid profiles in the RACF FACILITY general resource class. When the profiles are ready for all the MRO regions, test the production regions again with the new SVC and DFHIRP, this time using the FACILITY class profiles for logon and bind-time security checking.
6. Cutover to production with the new IRP
If the production MRO regions successfully log on to the new IRP with the new SVC, and bind-time security checking works successfully, use the new DFHIRP and SVC for the production regions.
7. Test MRO with CICS TS regions
With the production regions running successfully under the CICS TS SVC and IRP, you can initialize and test some CICS Transaction Server regions using MRO. These test regions can coexist in the same MVS image as the production regions, all using the same SVC and IRP.
Figure 3. Illustration of valid configurations using DFHIRP in a sysplex
 the figure illustrates SYSPLEX1, containing 3 MVS images MVSA,MVSB and MVSC. Each has several CICS releases running, and each has a different level of DFHIRP running in LPA.The following note provides the rest of the information.
Note:
All the CICS regions in SYSPLEX1 shown in Figure 3 can communicate across MRO links, because the DFHIRP in each MVS supports XCF/MRO.
[[ Contents Previous Page | Next Page Index ]]