SNAX/HLS Application Programming Manual

RECEIVE-CONTROL Verb
SNAX/HLS Verbs
5–64 104707 Tandem Computers Incorporated
7 (Name is DT–MESSAGE–CANCELLED.) The session partner has
canceled the current message. This value can be delivered only
under the LMO is Y condition. The current message is to be
disregarded.
8 (Name is DT–BIND–CINIT–DATA.) The session has just been
established. This message is delivered only if you specify the
WANT–BIND–DATA attribute as USER–DATA or ALL in the PROFILE
(see Section 4 of the SNAX/HLS Configuration and Control Manual),
and either a BIND or CINIT request was received. This message is
never received by applications that are establishing primary–acquire
sessions.
If you specify WANT–BIND–DATA as USER–DATA,
USER–DATA–LENGTH indicates the size of the user–data area on the
BIND or CINIT message; a value of 0 is possible.
If you specify WANT–BIND–DATA as ALL, the USER–DATA–LENGTH
indicates the length of the user text, requester–ID, and password
fields plus the three bytes. The minimum value is 3.
The USER–DATA–S field contains the following:
Length of requester–ID field (1 byte, value in binary)
Requester–ID field (in ASCII)
Length of password field (1 byte, value in binary)
Password field (in ASCII)
Length of user–text field (1 byte, value in binary)
User text (in ASCII)
This message is, in general, the first message your program receives.
It even precedes a response to HLS–OPEN in queued completion
mode. The only messages that might precede it are interrupt
messages.
In some cases (most noticeably, in TSO sessions), you might receive
two copies of the message because your partner issued a temporary
UNBIND command and then rebound the session.
9 (Name is DT–SESSION–CLOSED.) The session has just been closed
by partner. The message contains information indicating why the
session was closed. This message can be delivered only if you
created the session with the HLS–ALLOCATE and HLS–OPEN
verbs.