CMAS to CMAS link definitions - CMTCMDEF

The CMAS to CMAS link definition (CMTCMDEF) views display information about the direct LU 6.2 and MRO communication links between the local CMAS and any other CMASs.

Supplied views

To access from the main menu, click:

Administration views > CMAS configuration administration views > CMAS to CMAS link definitions

Table 1. Views in the supplied CMAS to CMAS link definitions (CMTCMDEF) view set
View Notes
CMAS to CMAS link definitions

EYUSTARTCMTCMDEF.CREATE

Create a new CMAS to CMAS link definition.
CMAS to CMAS link definitions

EYUSTARTCMTCMDEF.DETAILED

Detailed information about a link to a selected target CMAS.
CMAS to CMAS link definitions

EYUSTARTCMTCMDEF.REMOVE

Remove a CMAS to CMAS link definition from the data repository.
CMAS to CMAS link definitions

EYUSTARTCMTCMDEF.TABULAR

Tabular information about all CMAS to CMAS link definitions associated with the CMAS identified as the context.
CMAS to CMAS link definitions

EYUSTARTCMTCMDEF.UPDATE

Update a CMAS to CMAS link definition in the data repository.

Actions

Table 2. Actions available for CMTCMDEF views
Action Description
CREATE Create a new CMAS to CMAS link definition.
REMOVE Remove a CMAS to CMAS link definition from the data repository.
UPDATE Update a CMAS to CMAS link definition in the data repository.

Fields

Table 3. Fields in CMTCMDEF views
Field Attribute name Description
Last modification agent CHANGEAGENT The change agent identifier that made the last modification.
  • DREPAPI - Resource was last changed by a CICSPlex SM API command.
Last modification agent release CHANGEAGREL The CICS release level of the agent that made the last modification.
Last modification CHANGETIME The local time when the definition was last changed.
Last modification user ID CHANGEUSRID The user ID that made the last modification.
Time created CREATETIME The local time when the definition was created.
Description DESC A description of the CMAS-to-CMAS link.

Input Values: 1- to 58-character description

Description code page DESCCODEPAGE The code page of the description field.
LU 6.2 mode MODENAME For LU6.2 links, the VTAM mode table entry associated with the link.
Link protocol PROTOCOL The type of protocol used for this CMAS-to-CMAS link (LU62 or MRO).
Receive buffer size RECVBUF 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:

  • 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 two 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, re-create the definition on both sides, using the CMAS to CMAS link definition view, specifying appropriate buffer sizes.

  • 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.
MRO receive prefix RECVPFX 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.)
Type of attach-time security to be used SECATTACH 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-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 SECNAME For LU 6.2 links, a user ID to be associated with incoming transactions. If no value is specified the CICS default user ID is used.

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

Send buffer size SENDBUF 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.

Notes:

  • 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 two 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, re-create the definition on both sides, using the CMAS to CMAS link definition view, specifying appropriate buffer sizes.

  • 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.
MRO send prefix SENDPFX 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.)
Target system ID SYSID The CICS sysid of the target CMAS.
Target VTAM application ID TARGETAPPL The VTAM applid of the target CMAS.
Target CMAS TARGETNAME The name of a CMAS to which the local CMAS is linked.


eyua7df.html | Timestamp icon Last updated: Sunday, 4 June 2017