BIND Checking
During initialization of the LU-LU session, the host sends a BIND message to the Personal Communications LUA application that contains information such
as RU sizes to be used by the LU-LU session. Personal Communications returns this message to
the LUA application on an RUI_READ verb. It is the responsibility
of the LUA application to check that the parameters specified on the BIND are suitable. The application has the following options:
- Accept the BIND as it is, by issuing an RUI_WRITE verb containing an OK response to the BIND. No data needs to be sent on the response.
- Try to negotiate one or more BIND parameters (this is only permitted if the BIND is negotiable). To do this, the application issues an RUI_WRITE verb containing an OK response, but including the modified BIND as data.
- Reject the BIND by issuing an RUI_WRITE verb containing a negative response, using an appropriate SNA sense code as data.
See RUI Verbs, for more information on the RUI_WRITE verb.
Note: Validation of the BIND parameters,
and ensuring that all messages sent are consistent with them, is the responsibility
of the LUA application. However, the following two restrictions apply:
- Personal Communications and Communications Server reject any RUI_WRITE verb that specifies an RU length greater than the size specified on the BIND.
- Personal Communications and Communications Server require the BIND to specify that the secondary LU is the contention winner, and that error recovery is the responsibility of the contention loser.