Considerations
There are some considerations about the environment that affect its suitability for this technical solution.
- Scope and capacity of the environment
The environment must have sufficient scope and capacity to continue to work when the routing (TOR) regions and target (AOR) regions on one logical partition (LPAR) are shut down. This capacity is required so that work can be diverted to the remaining LPAR, without putting the remaining CICS regions under stress, or causing them to reach the limit of MXT (maximum tasks).
- Separation or affinities defined in the workload
When you shut down one LPAR, it is important that there are alternative regions on the other LPAR to which affinities and separation transactions can route.
- Use of z/OS Communications Server generic resources
The routing regions (TORs) are registered as z/OS Communications Server (previously known as VTAM) generic resources.
- Access to data
If you have database connections in certain regions, you must have sufficient capacity to connect to the database from other regions.
If you access data in one file-owning region (FOR), you must have alternative access to this data. If not, when you shut down the FOR to upgrade it, the CICS workload stops.
- Availability of a WUI server
It is not essential to have a WUI on each LPAR that is being upgraded, but it is helpful to monitor the systems and see the progress of the upgrade. Without a WUI server, the task of quiescing the application-owning regions (AORs) as routing targets must be performed through the CICSPlex SM application programming interface from batch or from a CICS application.