Designing your CICSPlex SM environment

Map out your enterprise to design a CICSPlex® SM environment that meets your system management requirements. Your design must include topology information, such as identifying the CICSplexes, CMASs, and WUI server regions that are required, as well as making other design decisions such as what naming convention to follow.

Before you begin

To design a CICSPlex SM environment, you must be familiar with the concepts and components of CICSPlex SM
Be aware of some considerations that can help to avoid issues with the set-up or maintenance of CICSPlex SM:
  • When you apply service to CICSPlex SM, PTFs that are applied to the ESSS are not intended to be downward-compatible with earlier maintenance levels at the same release. This means that all CMASes, MASes, WUI Server regions and API programs must run at the same maintenance level as the ESSS for their release. Otherwise, abends, data corruption and unexpected results might occur. When you apply PTFs to CICSPlex SM, it is essential that all ++HOLD ACTION items associated with the SMP/E maintenance are followed carefully.
  • Additionally, IBM suggests the following when you design a CICSPlex SM topology:
    1. Avoid running Production and non-Production (for example, Test, Development, or QA) regions on the same LPAR. All regions that run the same CICSPlex SM release use one copy of the ESSS: that is, they share the ESS. As a result, applying a PTF to this shared ESSS requires an outage of both the Production and the non-Production regions.
    2. Connect the WUI Server directly to the MP CMAS, so that they are both at the at the highest CICSPlex SM release level. This is to ensure that the WUI Server uses the highest resource tables and WUI views and generally simplifies upgrades. When you run a mixed release environment, it might be necessary to have more than one WUI Server. In that case, the advice here still applies; have one WUI server at the highest release level and connected directly into the MP CMAS, and any other lower release WUI Servers connected into the appropriate release CMAS, if required.
    3. Connect the MP CMAS only to other CMAS and a WUI server. Directly connecting MASes into the MP CMAS prevents the MP CMAS from being easily moved to a different LPAR in the event of an outage.
    4. Use a single Maintenance Point CMAS to prevent complexity during upgrades. For example, this helps avoid a potential conflict of CICSPlex SM release levels which can cause CMASes to be isolated from the management of a CICSplex during an upgrade.

Procedure

  1. Decide how to group your CICS® regions into system groups to identify what CICSplexes are required. The CICSplex is the largest unit that you can manage in your CICSPlex SM configuration.
  2. Decide how many CMASs are required for each CICSplex and how to link them together. The CMAS is the component of the CICSPlex SM topology that is responsible for most of the work involved in managing and reporting on CICS regions and their resources. Each CICSplex must have at least one CMAS.
  3. Decide how many WUI servers are required and how to link them to the correct CMAS.
  4. Decide on a naming convention for the CICSPlex SM components. The naming convention must be meaningful and extendable.
  5. Decide on an implementation strategy.

Results

Following these steps results in a detailed topology map of your enterprise.

What to do next

When you have completed your map of the enterprise, you are ready to plan the installation of CICSPlex SM to create your proposed configuration. Make sure that you keep your map up-to-date as you add more system groups or regions or make changes to the topology, because an accurate map makes it easier to maintain the CICSPlex SM configuration and topology data.


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