CMAS-to-CMAS links

When a CICSplex crosses multiple MVS images, multiple CMASs are likely to be involved in managing that CICSplex. The CMASs must be connected to each other (using CICS intercommunication methods) so that data relating to the CICS systems belonging to the CICSplex is accessible by all relevant CMASs, and an SSI can be presented to the CICS operator.

The minimum requirement is that CMASs managing the same CICSplexes be linked to form an open chain of CMASs, so that each CMAS is linked, if only indirectly, to every other CMAS. Meeting this requirement ensures that there is at least one path from each CMAS to every other CMAS involved in managing the same CICSplex. To achieve the best performance and availability, link every CMAS directly to every other CMAS.

Figure 2 illustrates the concept of direct and indirect CMAS-to-CMAS links.

The links between multiple CMASs involved in managing the same CICSplex are responsible for the SSI of the CICS® systems or systems that belong to that CICSplex. However, you do have a degree of choice regarding the number of links you define. First, here's a reminder of the rules and recommendations concerning CMAS-to-CMAS links:
  • To establish an SSI of a CICSplex, the CMASs managing that CICSplex should at the very least be linked to form an open chain.
    Figure 1. Adding CMASs to the enterprise map. A CMAS has been installed on each MVS image. CMAS 3 can issue SNA generic alerts to the NetView instance on the same MVS image. CMAS 3 is the maintenance point CMAS for CICSplex 1, and CMAS 5 is the maintenance point CMAS for CICSplex 2. (That is, CMAS 3 will be the context CMAS when you define CICSplex 1, and CMAS 5 will be the context CMAS when you define CICSplex 2 to CICSPlex SM.)
    The map shows the following systems: System A is an OS/390 2.10 system with a TOR and two AORs. System B is an OS/390 2.10 system with a TOR, a AOR and a FOR. System C is a z/OS 1.4 system with two CICS Transaction Server for OS/390 Release 2.3 AORs. System D is an OS/400 3.1 system with two CICS/400 3.1 regions. System E is an OS/390 version 2 release 10 system with two CICS Transaction Server for OS/390 Release 2.2 AORs and a CICS Transaction Server for OS/390 Release 1.3 AOR. System F is a z/OS 1.2 system with two AORs. The CICS regions from System A, System B and System C belong to CICSplex 1. The CICS regions from System E, and System F belong to CICSplex 2. The CICS regions from System D do not form part of a CICSplex. CMAS 1 is installed on System A. CMAS 2 is installed on system B. CMAS 3 is installed on System C. CMAS 4 is installed on system E. CMAS 5 is installed on System F. CMAS 3 and CMAS 5 are both maintenance point CMASs. CMAS 3 also has access to NetView.
    Figure 2. CMAS-to-CMAS links. This CICSplex is made up of six CICS systems, three managed by CMAS1 and three managed by CMAS5. In the absence of a direct link between the two CMASs, CICSPlex SM is able to navigate dynamically around its "network" to gather information relevant to the CICSplex. It could go via CMAS4 or, if CMAS4 is unavailable, for example, it could go via CMAS2 and CMAS3. For optimum performance, however, a direct link should be added between CMAS1 and CMAS5.
    The diagram shows five systems each managed by a CMAS. The CMASs are numbered 1 to 5. The CICSplex comprises six CICS regions, three of which are managed by CMAS1 and three by CMAS5. The intermediate systems are managed by CMAS2, CMAS3 and CMAS4. There are bi-directional links between CMAS1 and CMAS2, CMAS2 and CMAS3, CMAS3 and CMAS4, CMAS4 and CMAS5, and indirect bi-directional links between CMAS5 and CMAS3, and CMAS1 and CMAS4
  • The more links you establish, the better the performance. The best performance is achieved when every CMAS is directly connected to every other CMAS involved in the management of a single CICSplex.
  • A multiplicity of CMAS-to-CMAS links is also better for availability: if CMAS 1 is at the end of the chain and is connected to CMAS 2 only, the failure of CMAS 2 breaks the chain and leaves no connection to CMAS 1.
In the example configuration, full CMAS-to-CMAS connectivity is established for each of the two CICSplexes. That is, for management of CICSplex 1, CMASs 1, 2, and 3 are directly connected to each other; for management of CICSplex 2, CMASs 4 and 5 are directly connected to each other. Thus, eight CMAS-to-CMAS links must be defined:
CICSplex 1 CICSplex 2
CMAS1 to CMAS2 CMAS4 to CMAS5
CMAS1 to CMAS3 CMAS5 to CMAS4
CMAS2 to CMAS1  
CMAS2 to CMAS3  
CMAS3 to CMAS2  
CMAS3 to CMAS1  

You could have decided not to link CMAS 1 to CMAS 3 directly. This arrangement would have met the minimum CMAS-to-CMAS link requirement (by leaving us with an open chain of CMASs) and would have reduced the number of links to be defined by two. Had you done so, information requested from System C about CICS resources on System A, for example, would be obtained indirectly (via the adjacent CMAS, CMAS 2) rather than directly. Wherever full connectivity is not established among a group of CMASs, CICSPlex SM works out the quickest route to the requested data dynamically.

The performance impact is slightly higher when information is obtained indirectly, but this needs to be set against the overhead of setting up and maintaining the CMAS-to-CMAS links. In fact, even if you had defined one CICSplex rather than two in your example, full connectivity among the CMASs would have been feasible. (That is, you would have needed 20 CMAS-to-CMAS links, because the number of links required is n² - n, where n is the number of CMASs to be connected.) However, if you had ten CMASs managing a single CICSplex, the number of links required would jump to 90; if you had 15 CMASs, the number would be 210. In summary, you have to decide how many direct links you are prepared to define, and where indirect links can be accommodated, always remembering that the minimum requirement is for an open chain of CMAS-to-CMAS links.

Figure 1 shows the CMAS-to-CMAS links in the example configuration.

When there are multiple CMASs on the same MVS system, managing the same CICSplex, a local MAS that specifies only the CICSPLEX(name) CICSPlex SM system parameter, and not the CMASSYSID(name) CICSPlex SM system parameter, will connect to the last CMAS to initialize on the MVS image that manages the named CICSplex for a specific release of CICSPlex SM.



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