Upgrading a Web User Interface server

A Web User Interface server and the CMAS to which it connects must be at the highest level of CICSPlex® SM and CICS® in the CICSplex. They must be at the same level as the maintenance point CMAS. Web User Interface servers that have not yet been upgraded to the same level as the maintenance point CMAS can be used, but they might return unreliable results until you upgrade them.

1. Increase the size of the DFHTEMP data set, which is used in the COVC import process. The standard CICS sample has only a primary allocation, but include a secondary allocation for RECORDS, as shown in the following statements:

   //DEFTS    JOB accounting info,name 
   //AUXTEMP  EXEC PGM=IDCAMS 
   //SYSPRINT DD  SYSOUT=A 
   //SYSIN    DD  *    
              DEFINE CLUSTER(NAME(CICSTS52.CICS.CNTL.CICSqualifier.DFHTEMP)-
                     RECORDSIZE(4089,4089)            -                      
                     RECORDS(200 200)                 -           
                     NONINDEXED                       -           
                     CONTROLINTERVALSIZE(4096)        -           
                     SHAREOPTIONS(2 3)                -           
                     VOLUMES(volid))                  -         
                   DATA(NAME(CICSTS52.CICS.CNTL.CICSqualifier.DFHTEMP.DATA) -  
                     UNIQUE) 
   /*

2. With your Web User Interface server still running at your current release, use the export function of the COVC transaction to export your existing view set and menu definitions from the Web User Interface server repository (EYUWREP) to an extrapartition transient data queue. It is not necessary for the Web User Interface server to be connected to a CMAS. For information about exporting definitions, see Exporting WUI definitions and The Web User Interface server repository. You will use this information when you upgrade the contents of the Web User Interface server repository in a later process.
3. Authorize the Version 5.2 CICS and CICSPlex SM libraries. See Authorizing the CICS and CICSPlex SM libraries.
4. 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.
5. Upgrade the CSD file with the Version 5.2 group of resource definitions and CICS startup group list. For information about upgrading the CSD, 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 made any modifications to the dynamically created resource definitions for your earlier release that were supplied by CICSPlex SM in the EYU$WDEF sample, manually upgrade your modified resource definitions using the equivalents in the EYU$WDEF sample for Version 5.2. The safest way to do this is to copy the Version 5.2 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.
7. Edit the JCL used to start the Web User Interface server, changing library names for the previous release of CICSPlex System Manager to the Version 5.2 names. For information about the MAS startup JCL, see Changing startup JCL before starting a MAS.
8. 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.1 and later. This value may be tuned by the user in a similar manner to tuning CICS storage in a CMAS. 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.
9. Verify that the CICS system initialization parameter CPSMCONN=WUI is specified for the CICS region. This system initialization parameter initializes the CICS region as a Web User Interface server and dynamically creates the required resource definitions for CICSPlex SM.
10. Verify that the CICS system initialization parameter GRPLIST references the CICS-supplied default startup group list, DFHLIST, any CSD groups containing resource definitions that you have modified, and the lists of definitions for your own applications.
11. Ensure that you have deleted, redefined, and initialized the CICS local catalog and global catalog using the DFHCCUTL and the DFHRMUTL utility programs.
12. 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.
13. Upgrade the contents of the Web User Interface server repository (EYUWREP). During this process you will start the Web User Interface server at Version 5.2. See Upgrading the contents of the Web User Interface server repository (EYUWREP).