Upgrading a CICSPlex SM managed CICS system (MAS)

When you upgrade a CICSPlex® SM MAS to CICSPlex SM Version 5.2, you might choose to upgrade only the CICSPlex SM MAS agent. You are not required to upgrade the CICS® region to Version 5.2 at the same time.

1. If you use the link pack area (LPA), decide when you will replace the previous release modules in the LPA with the Version 5.2 modules. Every CICSPlex SM module installed in the LPA can be used only by the release of CICSPlex SM to which it relates.
   1. If you put the Version 5.2 modules in the LPA immediately, change your previous release MASs to use the previous release modules from the STEPLIB and DFHRPL concatenations, instead of the LPA.
   2. If you put the Version 5.2 modules in the LPA at the end of the upgrade process, make sure your upgraded MASs are using the Version 5.2 modules from the STEPLIB and DFHRPL concatenations instead of the LPA, then change them to use the LPA when you replace the modules.
   For more information, see Controlling the use of modules from the LPA.
2. If you made any modifications to the default resource definitions for your earlier release that were supplied by CICSPlex SM in the EYU$MDEF sample (which contains definitions for a MAS), or the EYU$WDEF sample (which contains definitions for a WUI), manually upgrade your modified resource definitions using the equivalents in the EYU$MDEF or EYU$WDEF sample for Version 5.2. The safest way to do this 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, and these might be inappropriate for CICS-supplied resource definitions.
3. In the JCL that is used to start the MAS, replace the previous release SEYUAUTH library name in the STEPLIB concatenation, and the previous release SEYULOAD library name in the DFHRPL concatenation, with the Version 5.2 SEYUAUTH and SEYULOAD library names. The Version 5.2 SEYUAUTH library must be authorized for APF, which you did when you upgraded the CMAS, but the SEYULOAD library must not be authorized. For information about the MAS startup JCL, see Changing startup JCL before starting a MAS.
4. Verify that the CICS system initialization parameter EDSALIM is specified for the CICS region, and set it to a value of 800 MB. 800 MB is the default EDSALIM value for a CICS region in Version 5.2. System initialization parameters can be specified before startup in the following locations:
   • In the system initialization table specified in the DFHSITxx load module whose suffix (xx) is specified as a SIT= system initialization parameter.
   • In the PARM parameter of the EXEC PGM=DFHSIP statement.
   • In the SYSIN data set defined in the startup job stream.
5. Verify that the CICS system initialization parameter CPSMCONN=LMAS is specified for the CICS region. This system initialization parameter initializes the CICS region as a MAS and dynamically creates the required resource definitions for CICSPlex SM. If you made any modifications to the dynamically created resource definitions in your previous release, you must manually upgrade these using the equivalents in the EYU$MDEF sample for Version 5.2.
6. If you use MAS history recording, define new history data sets using the EYUJHIST sample job. If you prefer to upgrade your existing history data sets, you can also do this using the EYUJHIST sample job by following the upgrading instructions, supplied as comments, in the sample. The EYUJHIST sample is supplied uncustomized in the TDFHINST library, and customized by DFHISTAR in the XDFHINST library. Remember to edit the MAS startup JCL to include the history data sets.
7. Optional: If you also want to upgrade the CICS region to Version 5.2 at this time, follow the instructions in Upgrade procedures for all CICS regions. You must upgrade the CSD for CICS as instructed, but you do not need to carry out any additional upgrade to your CSD to obtain the resource definitions for CICSPlex SM, because all CICSPlex SM resources are defined and installed dynamically.