Sharing CICS regions between region types in platforms

When you are designing your platform, you might decide to share some CICS® regions between multiple region types, either within a platform or between multiple platforms.

Sharing regions between region types can be a valuable configuration and easy to set up within a platform. Although there are more considerations than keeping everything separate, these can be made less severe with planning.

There are various reasons why you might want to share CICS regions. For example, in a platform on your development CICSplex, you may want to use a single CICS region that is shared by all of your region types. Using a single CICS region that is shared by all of your region types simplifies new development because you do not have to configure, manage and maintain multiple CICS regions. You might also want to share CICS regions in a production environment, where you have multiple platforms that share a single set of TORs or an FOR.

You can share CICS regions between region types either when you are setting up your platform, or in an installed and active platform. A created region type can only contain created CICS regions, and an adopted region type can only contain adopted CICS regions.

In created region types, you can clone certain region attribute values for all the CICS regions by specifying the attributes at a region type level, in the platform project. Platform design lists the options that you can set at this level, which relate to CICSPlex® SM workload management and BAS install. Shared CICS regions must be able to accept these settings from all the region types in which they are included. For example, you might create a region type that specifies that its CICS regions must be eligible as routing regions for workload management. This region type cannot share a CICS region with a region type where the CICS regions are required to be ineligible as routing regions. However, it can share a CICS region with a region type where the CICS regions are also required to be eligible as routing regions, or where that setting has not been specified at the region type level.

Whether you are sharing CICS regions within a platform or between multiple platforms, care must be taken to ensure that conflicts between specific CICS resources do not exist. Bundle installation for platforms and applications only checks for conflicts at the CICS bundle level. If two different bundles are installed into the same region and both create the same resource, the duplicated bundle part becomes unusable.

If multiple platforms are sharing a group of CICS regions, and both platforms require the same resources to be installed, only one of the platforms should attempt to install those bundles. This platform should be installed and discarded first. It is possible for both platforms to install the same set of bundles, but the results of this approach are uncertain. The platform install will state that no bundles were installed for the second platform. The second platform will show a platform ENABLESTATUS of INCOMPLETE, and bundle installation failures will also be recorded in the shared region. With this second approach, you also have to be careful about discarding a platform: because only one platform has the bundles installed, you must make sure that the other platform has the bundles installed that it needs to function. The worst case scenario with this technique is where both platforms are installed at the same time. In this case each platform may install a subset of the bundles and so both platforms will show a platform ENABLESTATUS of INCOMPLETE. However, even in this scenario, the platform will correctly clean up all of the bundles that are left behind when the platforms are discarded.



concept_sharing_regions.html | Timestamp icon Last updated: Sunday, 4 June 2017