Upgrading a CMAS

You must upgrade your CICSPlex® SM CMAS to Version 5.2 at the same time as you upgrade the CICS® system on which it runs. A CICSPlex SM CMAS runs only in a CICS system of the same release level. During startup, the CMAS checks the CICS release level and stops with message EYUXL0142 if the release does not match.

Before you begin

In a CICSplex that consists of CMASs at the Version 5.2 level and at one or more earlier levels, the maintenance point CMAS must be at the Version 5.2 level. So, when a CICSplex contains CMASs at more than one level, the first CMAS upgraded to Version 5.2 must be the maintenance point.

Before you upgrade a CMAS, check that the maintenance point CMAS for the CICSplex has been upgraded in every CICSplex where the CMAS is a member. Remove the CMAS from any CICSplex where the maintenance point CMAS is still at an earlier level. If the CMAS is started in a CICSplex that has a maintenance point CMAS at an earlier level, message EYUCP0012E is issued. In an environment with multiple interconnecting CICSplexes, this message and message EYUTS0012E can be issued repeatedly.

Note: When you upgrade a CMAS that is not a maintenance point CMAS, all of the CICSplex records are removed from its data repository. It cannot connect to its MASs, or join MASs connected to other CMASs, until it reconnects to its maintenance point, at which point its data repository is resynchronized for the CICSplex. Both the maintenance point and non-maintenance point issue EYULOG messages EYUCP0203I and EYUCP0204I. The data repository synchronize is not complete until both CMASs issue both messages. Depending upon the number of records in the CICSplex, the maintenance point usually takes longer than the non-maintenance point, and so the time between the two messages on the non-maintenance point is short, while the time between the two messages on the maintenance point is longer.

1. If the CMAS is running, stop it and upgrade the CICS modules to Version 5.2. For more information about dynamically updating DFHIRP, see Upgrading multiregion operation (MRO).
2. In the z/OS® image that contains the CMAS, verify that the IEASYSxx member of the SYS1.PARMLIB library that you use for z/OS initialization includes the MAXCAD and NSYSLX parameters, with an appropriate value. Specifying each CMAS correctly in IEASYSxx explains what values are suitable. If you are running both a previous release and Version 5.2 of CICSPlex SM, an Environment Services System Services (ESSS) space is started for each release, so you might need to modify the NSYSLX value.
3. Authorize the Version 5.2 libraries by adding them to the list of APF-authorized libraries in the appropriate PROGxx or IEAAPFxx member in SYS1.PARMLIB. See Authorizing the CICS and CICSPlex SM libraries.
4. Update the MVS linklist with the Version 5.2 modules that are required for CICS and CICSPlex SM. See Installing CICS required modules in the MVS link list.
5. Upgrade the CSD file with the Version 5.2 group of resource definitions and CICS startup group list. See Upgrading the CSD for CICS-supplied and other IBM-supplied resource definitions. You do not need to carry out an additional upgrade using a release-dependent set of definitions for CICSPlex SM.
6. If you modified the default resource definitions for your earlier release, supplied by CICSPlex SM in the EYU$CDEF sample (which contains definitions for a CMAS), manually upgrade your modified resource definitions using the equivalents in the EYU$CDEF sample for Version 5.2. The safest way is to copy the upgraded default resource definitions and reapply your modifications. It is important to upgrade your modified definitions to ensure that they are defined correctly with nondefault values for attributes that are new. If you fail to upgrade modified definitions, CICS assigns default values to any new attributes. The default values might be inappropriate for your requirements.
7. Edit the JCL used to start the CMAS, changing the previous release of CICSPlex SM library names to the Version 5.2 names. If you have BBACTDEF, BBVDEF, or BBIPARM DD statements in the JCL, delete them. For information about the CMAS startup JCL, see Preparing to start a CMAS.
8. Use the EYU9XDUT utility to upgrade the data repository (EYUDREP data set) for the CMAS to Version 5.2. For information about how to upgrade the data repository, see Creating the CICSPlex SM data repository. The conversion utility copies the contents of the existing data repository to a newly allocated data repository. The existing data repository is not modified.
   Note: After upgrading the data repository for the CMAS, the next time the CMAS is started it must point to the upgraded EYUDREP data set. If it does not, data repository updates might be lost. This loss can lead to incorrect results, which can include other CMASs isolating themselves when they connect to this CMAS. If after upgrading you choose to roll back to the version you upgraded from, use the EYU9XDUT utility to downgrade the upgraded data repository for the CMAS. Failure to do this could result in CMASs becoming isolated.
9. Delete, redefine, and initialize the CICS local catalog and global catalog using the DFHCCUTL and the DFHRMUTL utility programs.
10. Verify the CICSPlex SM system parameters referenced by the EYUPARM DD statement. If the CASNAME system parameter is present, delete it. For information about these parameters, see CICSPlex SM system parameters.
11. Verify that the CICS system initialization parameter GRPLIST references the CICS supplied default startup group list, DFHLIST, and any CSD groups containing resource definitions that were modified.
12. Verify that the maintenance point CMAS for the CICSplex is running in every CICSplex where the CMAS is a member, then perform a cold start of the upgraded CMAS. Allow the upgraded CMAS to perform repository synchronization with the other CMASs in the network. EYULOG messages EYUCP0203I and EYUCP0204I are issued when repository synchronization begins and completes. After repository synchronization is complete, you can proceed to upgrade the MAS regions that are connected to the CMAS.