Changes to installing

This section summarizes the changes to installation across supported releases of CICS TS for z/OS.
Table 1. Changes to installing, by release of CICS Transaction Server for z/OS
V3.2 V4.1 V4.2 V5.1 V5.2 V5.3
        CICS® checks during initialization for the required level of hardware.
          CICS checks during initialization that no CICS nucleus module comes from an earlier release than the release that is currently being started. This has an impact if you are using IBM HourGlass see DFHLD0110 during CICS TS 5.3 initialization when using HourGlass on dW Answers.
          DFHRPL libraries and dynamic program LIBRARY concatenations can be put in the EAS of EAV DASD.
        CICS TS comprises a base component and an activation module that is specific to the offering of CICS TS. Both must be installed.  
    Default size of auxiliary data sets changed from 1 cylinder to 25 cylinders, so the supplied SDFHINST JCL members DFHDEFDS, EYUCMSDS, and EYUCSYDS also changed.      
    The default location of JAVADIR is changed to support 64-bit JVM.      
CICS region user ID requires read access to each VSAM catalog for files for which CICS has installed file definitions.          
Integration of CICSPlex® SM and CICS installation: EYUISTAR process is obsolete and merged into the DFHISTAR process.          
APPLID of the CICS region must be unique across sysplex (or XRF-specific).          
MEMLIMIT must be set to 6 GB or greater.       CICS use of 64-bit storage has increased, therefore MEMLIMIT might need to be increased to avoid CICS SOS Above the Bar.