BIND
BIND is sent from the PLU to the SLU during session establishment. BIND indicates that the PLU wants to start a session with the SLU, and the request contains the session parameters that the PLU proposes to use for the session. The application program can issue OPNSEC to accept the session or SESSIONC CONTROL=BIND or TERMSESS OPTCD=UNBIND to reject the session. These macroinstructions can be issued either in the SCIP exit routine or in another part of the program after the SCIP exit routine returns to VTAM®. For more information on BIND, see Establishing and terminating sessions with logical units, especially BIND request, and BIND response. See Request and response exchanges for typical communication operations, for examples of BIND in various sequences, and Specifying a session parameter, for a description of the session parameters in BIND.
- Vector
- Description
- X'0E'
- Network-name control vector. Network-qualified name of the PLU.
- X'0E'
- Network-name control vector. Network-qualified name of the SLU.
- X'27'
- XRF session-activation control vector.
- X'2B'
- Route selection-control vector.
- X'2C'
- COS and TPF control vector.
- X'2D'
- Mode-name control vector.
- X'5F'
- Extended fully qualified PCID control vector.
- X'60'
- Fully qualified PCID control vector.
- X'66'
- Data compression control vector.
Refer to SNA Formats for a list of control vectors on BIND and their formats.
The read-only RPL's AAREA field points to the beginning of the control vectors attached to the BIND. The AAREA field is zero if there are no attached control vectors.
The length of the control vectors is determined as follows:
- PLU name field
- Crypto fields
- User data.
