Location of maintenance point CMAS

To manage resource definitions in a CICSPlex® SM context, the CICS® Configuration Manager server must be able to access that context. The server must run in a local MAS whose CMAS either:

For example, Figure 1 shows a topology where the CMAS for the CICS Configuration Manager server is the maintenance point for only one CICSPlex SM context, DEVT. Note that the data repository for this CMAS contains only the resource definitions for the DEVT context. The resource definitions for the other contexts are stored in other data repositories; the CMAS for the CICS Configuration Manager server routes updates to the appropriate maintenance point CMAS.

For best performance, the connections between CMASs should be via direct CMAS-to-CMAS links (as shown here). However, the connections can also be indirect, via a chain of CMAS-to-CMAS links.

Figure 1. The CMAS for the CICS Configuration Manager server must be linked, directly or indirectly, to all of the contexts that you want to manage

For information on defining CMAS-to-CMAS links, see the CICSPlex SM documentation.


Information Information

Feedback


Timestamp icon Last updated: Friday, 1 November 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//ccv-location-mp.htm