Most releases of CICS® make changes to the IBM-supplied groups of resource definitions that are included in the DFHLIST group list. In all such cases, the old versions of the CICS resource definitions are retained in compatibility groups, which are needed to support earlier releases if you share the CSD between different levels of CICS.
If, after upgrading a CSD, you plan to share the CSD with earlier releases of CICS, include the appropriate DFHCOMPx compatibility groups in your start-up group list to provide the required support for earlier releases. Table 10 shows you which DFHCOMP groups you need to include for the earlier releases. Do not attempt to share a CSD with a CICS region running at a higher level than the CSD.
It is important that you install the compatibility groups in the correct order, as shown in Table 10. For example, to run a CICS/ESA 4.1, with the CSD upgraded to CICS TS 3.1, append the compatibility group DFHCOMP9 followed by DFHCOMP8, DFHCOMP7, DFHCOMP6, and DFHCOMP5 at the end of your group list.
CICS release the CSD is shared with | The CICS release level of the CSD | ||||||
---|---|---|---|---|---|---|---|
CICS TS 3.1 | CICS TS 2.3 | CICS TS 2.2 | CICS TS 1.3 | CICS TS 1.2 | CICS TS 1.1 | 4.1 | |
CICS TS 2.3 | None | None | Do not share | Do not share | Do not share | Do not share | Do not share |
CICS TS 2.2 | DFHCOMPA | DFHCOMPA | None | Do not share | Do not share | Do not share | Do not share |
CICS TS 1.3 | DFHCOMP9 DFHCOMP8 | DFHCOMP9 DFHCOMP8 | DFHCOMP8 | None | Do not share | Do not share | Do not share |
CICS TS 1.2 | DFHCOMP9 DFHCOMP8 DFHCOMP7 | DFHCOMP9 DFHCOMP8 DFHCOMP7 | DFHCOMP8 DFHCOMP7 | DFHCOMP7 | None | Do not share | Do not share |
CICS TS 1.1 | DFHCOMP9 DFHCOMP8 DFHCOMP7 DFHCOMP6 | DFHCOMP9 DFHCOMP8 DFHCOMP7 DFHCOMP6 | DFHCOMP8 DFHCOMP7 DFHCOMP6 | DFHCOMP7 DFHCOMP6 | DFHCOMP6 | None | Do not share |
4.1 | DFHCOMP9 DFHCOMP8 DFHCOMP7 DFHCOMP6 DFHCOMP5 | DFHCOMP9 DFHCOMP8 DFHCOMP7 DFHCOMP6 DFHCOMP5 | DFHCOMP8 DFHCOMP7 DFHCOMP6 DFHCOMP5 | DFHCOMP7 DFHCOMP6 DFHCOMP5 | DFHCOMP6 DFHCOMP5 | DFHCOMP5 | None |
The REQUESTMODEL resource definition was introduced in CICS TS 1.3 to support inbound IIOP requests only. The REQUESTMODEL definition now supports both IIOP and EJB requests, and as a result is extended significantly, with many new attributes. At the same time, some of the old attributes are replaced, so that the keywords are meaningful for both EJB and IIOP, and to enable you to specify larger values.
The effect of all the changes is to make CICS TS 1.3 and CICS TS Version 2 REQUESTMODEL definitions incompatible when installing them in a CICS region. In other words, you cannot install a CICS TS 1.3 REQUESTMODEL in a CICS TS Version 2 region, and you cannot install a CICS TS Version 2 REQUESTMODEL in a CICS TS 1.3 region.
To ensure that you install the correct version of REQUESTMODEL resource definition in a CICS region, you are recommended to define the CICS TS 1.3 and CICS TS Version 2 REQUESTMODELs in separate groups in your CSD, and add the groups to the appropriate GRPLIST.
You can continue to update a CICS TS 1.3 REQUESTMODEL from a CICS TS Version 2 region using CEDA (or CEDB) in compatibility mode (using the PF2 function key in the CEDA ALTER panel), but in this mode you can only specify CICS TS 1.3 attributes. For example, if you specify any of the OMGxxxxxxxx attributes, CICS forces a blank CORBASERVER name. Other validation checks ensure that you cannot perform an invalid update when in compatibility mode. Also, to help ensure that you cannot install an incorrect version of a REQUESTMODEL, CICS rejects the install with an error message if you try to install a REQUESTMODEL with a blank CORBASERVER name in a CICS TS Version 2 region.
[[ Contents Previous Page | Next Page Index ]]