CMAS networks and registration

If more than one CMAS is involved in managing a CICSplex they must all be able to communicate with each other in order to implement single-system image.

This communication is also required to allow proper distribution of CICSPlex SM definitions from the maintenance point CMAS to other CMASs and to maintain the dynamic CICSplex topology. The maintenance point CMAS is responsible for maintaining the CICSplex definitions in the data repository as well as distributing them to other CMASs.

However, CMASs need not be fully interconnected. The CICSPlex SM communications component can deliver a request for remote processing even if the target is not directly connected to the CMAS or MAS where the request originates. The minimum requirement is that you can get from every CMAS to every other CMAS in the network via some route of CMAS-to-CMAS links, no matter how complex. Of course, performance may suffer if excessive transit nodes (those CMASs through which a request must pass on its way to the intended destination) are involved in a request. As a result, more than the minimum number of required communication links are often installed.

The CMAS provides information about the CICSplexes for which it can process requests to the ESSS address space that is running in its MVS™ image. This is necessary because ESSS establishes the connection between a CMAS and its local MASs. This connection is normally established when the MAS provides its name and the name of the CICSplex of which it is a member. So ESSS must be able to find a CMAS that manages the CICSplex named by a MAS.

Figure 1 shows a sample CMAS network and the service points that result.
Figure 1. A sample CMAS network
This sample CMAS network consists of 3 CMASs, each with 5 MASs. Each islinked to the other two. The service points for each CMAS are CMAS1, CMAS2, CMAS3 and PLEXA.


eyus1a0.html | Timestamp icon Last updated: Monday, 5 June 2017