Where to install CMASs
After you decide which CICS® systems are to be managed by CICSPlex® SM, and how they are to be organized into CICSplexes, you should think about where CMASs are required.
The rules and recommendations governing where a CMAS can, and must,
be installed are as follows:
- Each CICSplex must be managed by at least one CMAS.
- Each CICSplex must have a maintenance point CMAS.
- A CMAS can participate in the management of multiple CICSplexes.
The SDFH* libraries and the SEYU* libraries in the CMAS must be the same level, and the CMAS must be appropriate to the level of CICSPlex SM that you are running. See, 
- See, the appropriate Upgrading information set in the CICS information center.
- If you want CICSPlex SM to issue SNA generic alerts to a NetView® instance, a CMAS must be installed on the same MVS™ image as the NetView instance.
- Install one CMAS on each MVS image on which managed CICS systems are running.
- You can have more than one production CMAS in an MVS image, but it is unlikely to be necessary.
You should also consider the performance implications of your decision. Each CMAS has its space requirements and its own data repository.
If we apply these rules and recommendations to the example enterprise,
you can see that:
- You must have at least one CMAS in the enterprise.
- NetView is installed on System C; to send SNA alerts to that NetView instance, you must install a CMAS on the same MVS image.
Figure 1 shows the example map updated again, this time to show the application of these CMAS rules and recommendations.