If more than one CMAS is to be involved in the management of a CICSplex, you are recommended to create links between those CMASs. In this example, you will see how to define links between two CMASs, CMSSYS1 and CMSSYS2, which will both be involved in managing the CICSplex PLXPROD1.
Note that you must define the CMAS to CMAS links before defining CICSplex PLXPROD1 to the CMASs. If you define PLXPROD1 to the CMASs before creating the CMAS to CMAS links, a duplicate maintenance point condition is raised and the CMAS to CMAS connection is terminated.
The CMASs are running on separate MVS™ images, and their CASs (CASSYS1 and CASSYS2) are already connected. You have to create two links, one from CMSSYS1 to CMSSYS2, and one from CMSSYS2 back to CMSSYS1. Both CMASs should be running while you define these links.
The CMAS to CMAS link definition view is redisplayed, and includes an entry for the link you have just created. This confirms that the link from CMSSYS1 to CMSSYS2 has been defined in the data repository of CMSSYS1. Now you have to create the corresponding link from CMSSYS2 to CMSSYS1.
From the CMAS to CMAS link definition view, type CMSSYS2 into the CMAS context field and click Refresh. (Remember that you need to store this definition in CMSSYS2’s data repository, and so CMSSYS2 must be the context.)
The CMAS to CMAS link definition view is refreshed to show any CMAS to CMAS links that have already been defined to CMSSYS2.
A two-way link has now been created
between CMSSYS1 and CMSSYS2. The link is available immediately: you do not
have to restart the CMASs first. When the CMASs are restarted the required
definitions are created automatically during the CMAS startup.