Managing a CMAS configuration

CMAS configuration definitions are stored in the data repository associated with the CMAS identified as the maintenance point for the CICSplex. This maintenance point CMAS ensures that any other CMASs involved in managing the CICSplex also know about the configuration definitions.

Figure 1 illustrates the relationship between a CMAS configuration and the WUI views used to create and maintain that configuration.
Figure 1. Defining a CMAS configuration
This diagram shows a CMAS configuration consisting of CICSPlex EYUPLX01, and 4 associated MASs on the same z/OS image.
The CMAS configuration is maintained using the following views:
CMTCMDEF
Defines and maintains CMAS-to-CMAS links.
CPLXCMAS
Maintains CMAS associations with CICSplex es.
CPLEXDEF
Defines and maintains CICSplex definitions and CMAS associations.
BATCHREP
Defines and maintains data repository records.

Accessing CMAS configuration views in the Web User Interface

From the Web User Interface, you can access CMAS configuration views from the main menu by clicking Administration > CMAS configuration administration.

To display information about the CICSplexes associated with the local CMAS, from the main menu, click Administration > CMAS configuration administration > CICSplex definitions.

Additional views that you can use to manage configuration definitions are available when their associated CMASs or CICS® systems are active. You can get information about managing a CMAS configuration by clicking CICSPlex SM operations. From this menu, you can open the following CMAS configuration views:
  • CMASs known to local CMAS
  • CICSplexes managed by CMAS
  • CMASs managing CICSplex
  • CMAS to CMAS links
  • CMAS to MAS links

Online help is available for each view and for the fields in each view.

Remember: Unless noted otherwise, only the context setting is recognized when you are creating and maintaining configuration definitions. For additional information about setting the context to a CMAS, see Setting the CMAS context, context and scope.