com.ibm.cics.model

Interface ICMASToCMASLinkDefinition

    • Method Detail

      • getTargetname

        java.lang.String getTargetname()
        Getter for field TARGETNAME

        Target CMAS

        The name of a CMAS to which the local CMAS is linked.

      • getTargetappl

        java.lang.String getTargetappl()
        Getter for field TARGETAPPL

        Target VTAM application ID

        The VTAM applid of the target CMAS.

      • getSysid

        java.lang.String getSysid()
        Getter for field SYSID

        Target system ID

        The CICS sysid of the target CMAS.

      • getModename

        java.lang.String getModename()
        Getter for field MODENAME

        LU 6.2 mode

        For LU6.2 links, the VTAM mode table entry associated with the link.

      • getRecvpfx

        java.lang.String getRecvpfx()
        Getter for field RECVPFX

        MRO receive prefix

        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.)

      • getSendpfx

        java.lang.String getSendpfx()
        Getter for field SENDPFX

        MRO send prefix

        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.)

      • getDescription

        java.lang.String getDescription()
        Getter for field DESC

        Description

        A description of the CMAS-to-CMAS link.

        Input Values: 1- to 58-character description

      • getSendbuf

        java.lang.Long getSendbuf()
        Getter for field SENDBUF

        Send buffer size

        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.
      • getRecvbuf

        java.lang.Long getRecvbuf()
        Getter for field RECVBUF

        Receive buffer size

        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.
      • getSecattach

        java.lang.String getSecattach()
        Getter for field SECATTACH

        Type of attach-time security to be used

        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.
      • getSecname

        java.lang.String getSecname()
        Getter for field SECNAME

        User ID of remote system for security purposes

        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.

Copyright ? 2008-2015 IBM Corp. All Rights Reserved.