CMAS configuration definitions and their related views

Figure 28 illustrates the relationship between a CMAS configuration and the end user interface views used to create and maintain that configuration. It also shows that CMAS configuration definitions are stored in the data repository associated with the CMAS identified as the maintenance point for the CICSplex. This CMAS ensures that any other CMASs involved in managing the CICSplex also know about the configuration definitions.

Figure 28. Defining a CMAS configuration
 This diagram shows a CMAS configuration consisting of CICSPlex EYUPLX01,and 4 associated MASs on the same MVS image, . This configuration is maintained using the following views:  CMTCMDEF -- to define and maintain CMAS-to-CMAS links, CPLXCMAS -- to maintain CMAS associations with CICSplexes, CPLEXDEF -- to define and maintain CICSplex definitions and CMAS associations, BATCHREP -- to define and maintain data repository records.

Additional views that you can use to manage configuration definitions once their associated CMASs or CICS® systems are active are identified in Table 4, and are described in Managing a CMAS configuration.

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

You can access a configuration view by:

Figure 29. The ADMCONFG menu
 27FEB2005  16:50:40 ----------- INFORMATION DISPLAY ---------------------------
 COMMAND  ===>                                                 SCROLL ===> PAGE
 CURR WIN ===> 1        ALT WIN ===>
  W1 =MENU==============EYUPLX01=EYUPLX01=27FEB2005==16:50:40=CPSM==========6===
 CMD Name             Description
 --- -------------------------------
     ADMCONFG   CMAS Configuration Administration Views
       BATCHREP   Batched Repository Updates
       CPLEXDEF   CICSplex Definitions
       CPLXCMAS   CMAS in CICSplex Definitions
       CMTCMDEF   CMAS-to-CMAS Link Definitions
       CMTPMDEF   CMAS-to-RMAS Link Definitions
 
 

For additional information about accessing these views, see Accessing end user interface administration views.

Reminders:

The remainder of this chapter contains detailed descriptions of the CMAS configuration views.

BATCHREP (Batched repository-update facility)

The batched repository-update facility allows you to create, update, remove, list, or dump one or more definitions from the data repository associated with the local CMAS. This is described in topic Using the batched repository-update facility.

Notes:
  1. When definitions are listed or dumped, they can be modified and used as input to the data repository. For more information about creating and maintaining the data repository, see Using the batched repository-update facility.
  2. CMAS-related definitions can be updated on any local CMAS. However, definitions related to the CICSplex must be processed on the maintenance point CMAS.
Start of change

Managing CMAS to CMAS links using the Web User Interface

Start of changeTo manage the direct LU 6.2 and MRO communication links between the local CMAS and any other CMAS click Administration views-->CMAS configuration administration views-->CMAS to CMAS link definition. This view allows you to create update and remove links. In order to create a link between CMASs, each must have a WUI attached.End of change

Creating CMAS to CMAS links

Follow this procedure to create a link definition to another CMAS and add it to the data repository of the local CMAS.

  1. Open the CMAS to CMAS link definition view, which displays any existing links in tabular form. If you want to base a new link definition on an existing link, select a link definition using the adjacent check box.
  2. Click the Create action button at the bottom of the view.

    The CMAS to CMAS link definitioncreate panel (EYUSTARTCMTCMDEF.CREATE) is displayed. If you first selected an existing link definition, this panel contains values from the selected link.

  3. Fill in the Create panel by supplying (or overtyping) the following information:
    Target CMAS Name
    Specify the 1- to 8-character name of the CMAS to which you want to establish a link.
    Description
    Specify a 1- to 30-character description of the link.
    Target application ID
    Specify the VTAM® APPLID for the target CMAS.
    Target system ID
    Specify the 1- to 4-character system ID of the CMAS to which you want to establish a link. The valid characters for a system ID are A - Z and 0 - 9.

    Start of changeThis name must match the name specified via the SYSIDNT parameter in the CICS system initialization table (SIT). .End of change

    Link protocol
    Specify the protocol to be used as either LU62 or MRO.
    Send buffer size
    Specify the size of the send buffer for the link, in the range 256 - 30720. The size specified should be 36 bytes less than the smallest MAXDATA value in any NCP through which the link may pass. The 36 bytes provides allowance for VTAM required headers.
    Note:
    For MRO, the SENDSIZE and RECEIVESIZE values on a connection are mostly ignored by CICS, especially when the only use of the connections is CICS DTP (which is the model that CMAS to CMAS communications uses). Therefore, it does not really matter what it is set to. More important for MRO links is IOAREALEN. However, with a CMAS to CMAS link definition you cannot change the IOAREALEN used on the SESSIONS definition that is subsequently installed in the CMAS. CICSPlex® SM sets the IOAREALEN of MRO SESSIONS definitions to 8192, which is the maximum size of the buffer that CMAS to CMAS communications uses.
    Receive buffer size
    Specify the size of the receive buffer for the link, in the range 256 - 30720. The size specified should be 36 bytes less than the smallest MAXDATA value in any NCP through which the link may pass. The 36 bytes provides allowance for VTAM required headers.
    Notes:
    1. If the values specified for the Send and Receive buffers are too large for VTAM, VTAM errors cause attempted connections to fail. In fact, soon after the 2 CMASs connect, the connection is timed out. Connections can be reestablished, but they will continue to time out. When this occurs, verify that the specified buffer sizes are within the guidelines listed here.

      When the buffer sizes are not as recommended, recreate the definition on both sides, using the CMAS to CMAS link definition view, specifying appropriate buffer sizes.

    2. For MRO, the SENDSIZE and RECEIVESIZE values on a connection are mostly ignored by CICS, especially when the only use of the connections is CICS DTP (which is the model that CMAS to CMAS communications uses). Therefore, it does not really matter what these are set to. More important for MRO links is IOAREALEN. However, with a CMTCMDEF you cannot change the IOAREALEN used on the SESSIONS definition that is subsequently installed in the CMAS. CICSPlex SM sets the IOAREALEN of MRO SESSIONS definitions to 8192. This is the maximum size of the buffer that CMAS to CMAS communications uses.
    Note:
    LU 6.2 mode name
    (Required for LU 6.2 connections.) Specify the 1- to 8-character VTAM LOGMODE name that identifies the group of related sessions. If you do not specify a name, the field will contain blanks, which is a valid name.
    MRO receive prefix
    Specify the 2-character prefix that is used as the first two characters of the Terminal Control Table Terminal Entry (TCTTE) names. Be careful that the prefix does not cause a TCTTE name to be generated that matches an existing connection or terminal name. (Required for MRO connections only.)
    MRO send prefix
    Specify the 2-character prefix that is used as the first two characters of the TCTTE names. Be careful that the prefix does not cause a TCTTE name to be generated that matches an existing connection or terminal name. (Required for MRO connections only.)
    Type of attach--time security
    Specify the source of the user ID(s) to be associated for incoming transactions on the link as:
    LOCAL
    The user ID associated with incoming transactions is the value associated with the Security Name field.
    IDENTIFY
    The user IDs associated with incoming transactions are the following:
    • The system already verified user ID received from the target system, or the CICS default user if none is received.
    • The user ID associated with the Security Name field.
    User ID of remote system for security purposes
    (Optional.).

    For MRO links this value is ignored and the Security Name value used is the CICS region user ID associated with the target system.

    For LU 6.2 links specify a user ID to be associated with incoming transactions. If no value is specified the CICS default user ID is used.

    If transaction security is active in the CMAS, the user ID associated with the Security Name field needs to have access to attach the transactions listed in CICS RACF® Security Guide.

    Depending on your requirements security administration may be simpler if the CICS region user ID or PLTPIUSR is specified for the CMAS.

    For further details about the Security Name field and its relationship with the Attach Security field see the CICS RACF Security Guide.

  4. Click Yes at the bottom of the Create panel to add the link definition to the data repository of the local CMAS.
  5. Repeat this procedure for each CMAS with which the local CMAS is to have direct communication. Then, change the context to another CMAS and repeat this procedure for that CMAS. For example, to establish two-way communication between EYUCMS1A and EYUCMS1B, first set the context to EYUCMS1A and define a link to EYUCMS1B. Then, change the context to EYUCMS1B and define a link to EYUCMS1A.

    The CICS resource definitions needed to establish communication with the designated CMAS are installed automatically using EXEC CICS CREATE interface.

Updating a CMAS to CMAS link definition description

Follow this procedure to update a CMAS to CMAS link definition description in the data repository.

  1. Select a link definition from the CMAS to CMAS link definition view and click the Update action button.

    The CMAS to CMAS link definition create panel is displayed containing details of the selected link. You can modify only the Description field.

  2. Update the description and click Yes to update the link definition in the data repository.

Removing a CMAS to CMAS link definition description

Follow this procedure to remove a CMAS link definition from the data repository of the local CMAS. When you do this, the appropriate CICS resource definitions are automatically removed from the CICS system definition (CSD) file for that CMAS.

  1. Select a link definition from the CMAS to CMAS link definition view and click the Remove action button.

    A confirmation panel is displayed.

  2. Click Yes to remove the link definition from the data repository or click No to return.
End of change

Managing CMAS to CMAS links using the end-user interface

To display information about the direct LU 6.2 and MRO communication links between the local CMAS and any other CMASs, issue the command:

   CMTCMDEF [cmas]

where cmas is the specific or generic name of a CMAS defined to the local CMAS. If this parameter is omitted, the view, illustrated in Figure 30, includes information about all CMASs defined to that CMAS.

Figure 30. The CMTCMDEF view
 27FEB2005  17:26:32 ----------- INFORMATION DISPLAY ---------------------------
 COMMAND  ===>                                                 SCROLL ===> PAGE
 CURR WIN ===> 1        ALT WIN ===>
  W1 =CMTCMDEF=CMTCMDEF=EYUCMS1A=EYUCMS1A=27FEB2005==17:26:30=CPSM==========1===
 CMD Target   Sys                Sess
 --- CMAS---- Id-- Applid   Type Prfx- Modename Description-------------------
     EYUCMS1B CM1B EYUCMS1B LU62                Starter Set CMAS on System B
 
 

Action commands

Table 16 summarizes the action commands you can use with the CMTCMDEF view.

Table 16. CMTCMDEF view action commands
Primary command Line command Description
n/a BRO Browse a link definition in the data repository.

The format of the resulting, nonmodifiable panel is identical to that shown in Figure 31.

CREate CRE Create a link definition to another CMAS and add it to the data repository of the local CMAS, as described in topic Creating a CMAS-to-CMAS link definition.

When you use the primary command CREate, some fields in the new view may contain values supplied by CICSPlex SM; you may change these values. When you enter the line command CRE next to the name of a link definition, fields in the new view contain values to be modelled (from the existing link definition).

n/a REM Remove a CMAS link definition from the data repository of the local CMAS.
n/a UPD Update a link definition in the data repository.

The format of the resulting panel is identical to the panel shown in Figure 31. You can modify the contents of only the Description field.

You can use the CMTCMLNK or CMTCMLND view, as indicated in Table 4, to discard a link definition without removing it from the data repository.

Hyperlink fields

There are no hyperlink fields for the CMTCMDEF view.

Creating a CMAS-to-CMAS link definition

Figure 31 shows the format of the panel produced when you use the create primary (CREate) or line (CRE) action command from the CMTCMDEF view.

Figure 31. Creating a CMAS-to-CMAS link
 ------------------------- Define CMAS Link for EYUCMS01 -----------------------
 COMMAND  ===>
 
  Target CMAS Name ===>
 
  Description      ===> Starter Set CMAS on System B
 
  Target Applid    ===> EYUCMS1B    Target CMAS VTAM Applid
  Target Sysid     ===> CM1B        Sysid of Target CMAS
 
  Protocol         ===> LU62        Connection Type (LU62/MRO)
  Send Buffer      ===> 8192        Size of send buffer (256 - 30720)
  Receive Buffer   ===> 8192        Size of receive buffer (256 - 30720)
 
  Modename         ===>             Modename for LU62 Link
  Receive Prefix   ===>             Unique 2 character prefix for MRO
  Send Prefix      ===>             Unique 2 character prefix for MRO
 
  Attach Security  ===> LOCAL       Attach User Security (LOCAL/IDENTIFY)
  Security Name    ===>             Userid associated with link
 
 
Press Enter to define CMAS Link with the options specified.
Type END or CANCEL to cancel without defining.

Provide the information as described in Creating CMAS to CMAS links and press Enter to add the link definition to the data repository of the local CMAS.

Repeat this procedure for each CMAS with which the local CMAS is to have direct communication. Then, change the context to another CMAS and repeat this procedure for that CMAS. For example, to establish two-way communication between EYUCMS1A and EYUCMS1B, first set the context to EYUCMS1A and define a link to EYUCMS1B. Then, change the context to EYUCMS1B and define a link to EYUCMS1A.

Start of changeThe CICS resource definitions needed to establish communication with the designated CMAS are installed automatically using EXEC CICS CREATE interface.End of change

Start of change

CMAS to MAS links

Start of changeA CMAS can communicate with other MASs.

End of changeEnd of change

CICSplex definitions

A CICSplex consists of one or more CICS systems or CICS system groups and is managed by one or more CMASs. Establishing a CICSplex requires that you:

Start of change

Managing CICSplex definitions using the Web User Interface

To display information about the CICSplexes associated with the local CMAS click Administration views-->CMAS configuration administration views-->CICSplex definition. This view lists summary information of the CICSplexes defined to the local CMAS in tabular form. To view details of one of the listed CICSPlexes, select from the Record column the adjacent check box. The CICSplex definition view includes action buttons that allow you to do the following:

Creating a CICSplex definition

Follow this procedure to create a CICSplex definition and add it to the data repository.

  1. Open the CICSplex definition tabular view. If you want to base a new link definition on an existing link, select a link definition using the adjacent check box.
  2. Click the Create action button at the bottom of the view.

    The CICSplex definition create panel is displayed. If you first selected an existing link definition, this panel contains values from the selected link.

  3. Fill in the create panel by supplying (or overtyping) the following information:
    CICSplex name
    Specify a 1- to 8-character name for the CICSplex that is unique within your CICSPlex SM environment. The name can contain alphabetic, numeric, or national characters. However, the first character must be alphabetic.
    Notes:
    1. The name of a CICSplex should not be the same as the name of a CMAS, a CICS system, a CICS system group, or another CICSplex at your enterprise.
    2. If a CICSplex with the same name is defined to any other CMAS and that CMAS attempts to communicate with the local CMAS, all direct and indirect communication links between the two CMASs are automatically removed.
    CICSPlex description
    Specify a 1- to 30-character description of the CICSplex.
    Monitor interval
    Specify the number of minutes during which monitoring data is to be collected and accumulated before the statistics counters are reset. The value must be:
    • Between 15 and 1440 and evenly divisible into 1440. If you specify a value that is not evenly divisible into 1440, you are prompted for one that is.
    • Omitted, when you want to use the default interval value of 480 minutes (8 hours).
    Note:
    The Monitor Interval can be updated using the update action. However, when you do so, the new value does not take effect in a MAS until that MAS is shut down and restarted.
    Daylight savings in effect
    Specify Yes or No to indicate whether you currently recognize daylight saving time.
    Time zone
    Specify one of the codes shown in Table 32 to identify the time zone that is associated with this CICSplex. For more information about the time zone attributes and how to use them, see CICSPlex SM time zone attributes
    Time Zone offset
    Specify a value between 0 and 59 to identify the number of minutes to be added to the time for that time zone (for areas that do not use a standard time zone).
    Resource status facility population
    Specify Yes or No to indicate whether the CICSplex is to be reported to the resource status facility.
    Simulated CICS command security checking
    Specify Yes or No to indicate whether or not CICSPlex SM security checking is to simulate CICS command checking for the CICS systems associated with this CICSplex. (If you do not specify a value, the default is NO.)
    Simulated CICS resource security checking
    Specify Yes or No to indicate whether or not CICSPlex SM security checking is to simulate CICS resource checking for the CICS systems associated with this CICSplex. (If you do not specify a value, the default is NO.)
    Security checking exemption
    Specify Yes or No to indicate whether or not simulated CICS security checking is to be bypassed for specific users or resources in this CICSplex. (If you do not specify a value, the default is NO.)
  4. Click Yes to add the CICSPlex defintion to the data repository.

There is no restriction on the number of CICSplexes that you can associate with a single CMAS.

The CICSplex becomes available as soon as its definition is added to the data repository for the local CMAS.

Assigning a CMAS to a CICSplex

Follow this procedure to add a CMAS to a CICSPlex definition in the data repository.

When a CICSplex is to be managed by multiple CMASs, the CMAS in effect when you create the CICSplex becomes the maintenance point CMAS for that CICSplex. There is no restriction on the number of CMASs that can be involved in the management of a single CICSplex.

  1. Open the CICSplex definition tabular view and select the CICSPlex you wish to assign.
  2. Click the Assign action button.

    The CICSplex definition assign panel is displayed.

  3. Specify the 1- to 8-character name of the CMAS that is to be associated with the designated CICSplex
  4. Click Yes to confirm the operation or No to cancel.

    The specified CMAS is added to the CICSPlex definition in the data repository and the CICSplex definition tabular view is redisplayed.

End of change

Managing CICSplex definitions using the end-user interface

To display information about the CICSplexes associated with the local CMAS, issue the command:

   CPLEXDEF [cicsplex]

where cicsplex is the specific or generic name of a CICSplex known to the local CMAS. If this parameter is omitted, the view, illustrated in Figure 32, includes information about all CICSplexes that are associated with that CMAS.

Figure 32. The CPLEXDEF view
 27FEB2005  18:22:02 ----------- INFORMATION DISPLAY ---------------------------
 COMMAND  ===>                                                 SCROLL ===> PAGE
 CURR WIN ===> 1        ALT WIN ===>
  W1 =CPLEXDEF==========EYUCMS1A=EYUCMS1A=27FEB2005==18:22:00=CPSM==========1===
 CMD Name     Mon  Time Zone Day  Cmd Res  Xmp Res Description
 --- -------- Intv Zone Adj  Save Chk Chk  Chk Sta ----------------------------
     EYUPLX01  480 Z       0 NO   NO  NO   YES YES Starter Set Plex 1 on System
 
 
Action commands

Table 17 summarizes the action commands you can use with the CPLEXDEF view.

Table 17. CPLEXDEF view action commands
Primary command Line command Description
n/a ADD Add a CMAS to a CICSplex definition in the data repository, as described in topic Adding a CMAS to a CICSplex.
n/a BRO Browse a CICSplex definition in the data repository.

The format of the resulting, nonmodifiable panel is identical to that shown in Figure 33.

CREate CRE Create a CICSplex definition and add it to the data repository, as described in topic Creating a CICSplex definition. The CMAS that is the current context becomes the maintenance point CMAS.
n/a REM Remove a CICSplex definition from the data repository.
Note:
When you remove a CICSplex definition, all of its topology, workload management, real-time analysis, resource monitoring, and business application services definitions are also removed. When multiple CMASs are involved in managing the CICSplex, these definitions are removed from the data repository associated with each CMAS.
n/a UPD Update a CICSplex definition in the data repository.

The format of the resulting panel is identical to the panel shown in Figure 33. You can modify the contents of any field in the panel except the CICSplex definition name.

Hyperlink fields

Table 18 shows the hyperlink field on the CPLEXDEF view.

Table 18. CPLEXDEF view hyperlink field
Hyperlink field View displayed Description
Name CPLXCMAS Information about the CMASs linked to the specified CICSplex
Creating a CICSplex definition

Figure 33 shows the format of the panel produced when you use the create primary (CREate) or line (CRE) action command from the CPLEXDEF view.

Figure 33. Creating a CICSplex definition
 ------------------------- Create CICSPlex for EYUCMS1A ------------------------
 COMMAND  ===>
 
 CICSPlex name          ===>
 Description            ===>
 
 Monitor Interval       ===> 480    Performance interval duration (15-1440 min)
 Daylight Savings Time  ===> NO     YES or NO
 Time Zone              ===> B      Time zone for interval (B-Z)
 Time Zone Adjustment   ===> 0      Offset from time zone (0-59)
 Resource Status                    Operational status for resource
        Facility        ===> NO       status facility (NO, YES)
 CICS Command Checking  ===> NO     Simulated CICS Command Checks
 CICS Resource Checking ===> NO     Simulated CICS Resource Checks
 Exemption Checking     ===> YES    Check for Exempt Users
 
  
Press ENTER to create CICSplex.
Type END or CANCEL to cancel without creating.

Provide the following information described in Creating a CICSplex definition. For more information about the time zone attributes and how to use them, see CICSPlex SM time zone attributes. Press Enter to add this definition to the data repository.

There is no restriction on the number of CICSplexes that you can associate with a single CMAS.

The CICSplex becomes available as soon as its definition is added to the data repository for the local CMAS.

Adding a CMAS to a CICSplex

When a CICSplex is to be managed by multiple CMASs, the CMAS in effect when you create the CICSplex becomes the maintenance point CMAS for that CICSplex. There is no restriction on the number of CMASs that can be involved in the management of a single CICSplex.

Figure 34 illustrates the panel produced when you use the add (ADD) line action command from the CPLEXDEF view.

Figure 34. Adding a CMAS to a CICSplex
 ------------------------ Add CMAS to CICSPlex for EYUCMS1A --------------------
 COMMAND  ===>
 
  CICSPlex name         EYUPLX01
  Description           Starter Set Plex 1 on System A
 
  CMAS Name        ===>            Name of CMAS or Generic
 
Press Enter to add CMAS to CICSplex.
Type END or CANCEL to cancel without adding.
 

Specify the 1- to 8-character name of the CMAS that is to be associated with the designated CICSplex. Press Enter to add this information to the data repository.

CPLXCMAS (CMASs associated with a CICSplex)

To display information about CMASs associated with a CICSplex, where the local CMAS must be the maintenance point for that CICSplex, issue the command:

   CPLXCMAS [cicsplex]

where cicsplex is specific or generic name of a CICSplex known to the local CMAS. If this parameter is omitted, the view, illustrated in Figure 35, includes information about all CICSplexes that are associated with that CMAS.

Figure 35. The CPLXCMAS view
 27FEB2005  18:22:17 ----------- INFORMATION DISPLAY ---------------------------
 COMMAND  ===>                                                 SCROLL ===> PAGE
 CURR WIN ===> 1        ALT WIN ===>
  W1 =CPLXCMAS==========EYUCMS1A=EYUCMS1A=27FEB2005==18:22:17=CPSM==========2===
 CMD CICSPlex CMAS
 --- Name---- Name---- MP  State---
     EYUPLX01 EYUCMS1A YES NORMAL
     EYUPLX01 EYUCMS1B NO  NORMAL
 

You can use the CICSPLEX view, as indicated in Table 4, to display status information about CMASs associated with a CICSplex, where the local CMAS need not be the maintenance point for the CICSplex.

Action commands

Table 19 summarizes the action commands you can use with the CPLXCMAS view.

Table 19. CPLXCMAS view action commands
Primary command Line command Description
n/a BRO Browse the definition of the association between a CICSplex and the maintenance point CMAS in the data repository.

Figure 36 illustrates the panel produced when you issue the BROwse command from the CPLXCMAS view.

n/a FOR Force an inaccessible CMAS associated with a CICSplex to be removed.
n/a REM Remove a CMAS associated with a CICSplex.
Figure 36. The BROwse panel for CPLXCMAS
 ------------------------ Browse CPLXCMAS for CMAS EYUCMS1B --------------------
 COMMAND  ===>
 
  CICSplex name         EYUPLX01
 
  CMAS Name             EYUCMS1B
 
  Maintenance Point     YES
 
  State                 NORMAL
 
Type END or CANCEL to cancel browse.
 

When you remove a CMAS from a CICSplex definition, the action command you use depends on whether the CMAS to be removed is currently accessible to the local CMAS.

In most cases, you should use the REM action command because the CMAS normally is or will become accessible to the local CMAS.

Note:
You cannot remove the association between a CICSplex and its maintenance point CMAS. If you determine that a different CMAS should be the maintenance point for a CICSplex, you need to perform the following steps:
  1. With the context set to the maintenance point CMAS, use the CPLXCMAS view to remove any nonmaintenance point CMASs from the CICSplex, as described in topic Action commands.
  2. With the context still set to the maintenance point CMAS, use the CPLEXDEF view to remove the CICSplex, as described in topic Action commands.
  3. Change the context to the appropriate CMAS.
  4. Redefine the CICSplex to the new maintenance point CMAS, as described in topic Creating a CICSplex definition.
  5. Add other CMASs to the CICSplex, as described in topic Adding a CMAS to a CICSplex.

Hyperlink fields

Table 20 shows the hyperlink field on the CPLXCMAS view.

Table 20. CPLXCMAS view hyperlink field
Hyperlink field View displayed Description
CICSplex Name CPLEXDEF Information about the specified CICSplex.
[[ Contents Previous Page | Next Page Index ]]