SNAX/HLS Application Programming Manual

RECEIVE DATA Verb
SNAX/HLS Verbs
5–86 104707 Tandem Computers Incorporated
Table 5-3 reflects the value delivered to this field:
Table 5-3. Definite–Response Indicators
Value Delivered to Application Program
DR and ER Bits on SNA Message ENCODE–ERI = N ENCODE–ERI = Y
None 0 0
DR1 1 1
DR2 2 2
DR1 & DR2 3 3
DR1 & ERI 1 5
DR2 & ERI 2 6
DR1 & DR2 & ERI 3 7
DATA–TYPE–RECEIVED
is a computational value indicating the kind of data that was received. The codes
are as follows:
negative An FMH header is present in the data. The absolute value of
DATA–TYPE–RECEIVED is the type of the FMH header (for example,
–1 indicates FMH type 1, –2 indicates FMH type 2, and so on. The
special value of –128 indicates FMH type 0).
0 (Name is DT–PARTNER–DATA.) The message is from the session
partner
1 (Name is DT–INTERRUPT–REQUEST.) The message is an interrupt
message, originating usually from the use of the OMSG statement in
HLSCOM.
2 (Name is DT–SSCP–DATA.) The message is from the session partner’s
SSCP. This can occur only if the attribute has been explicitly enabled
in the WANT–SSCP–TEXT attribute of the PROFILE.
3 (Name is DT–PREPARED–TO–CLOSE.) The session partner is
prepared for session termination.
4 (Name is DT–LU–STATUS.) LUSTAT has been received from the
session partner. This might indicate SNA information or session–
partner unique information.
5 (Name is DT–SIGNAL.) The session partner has sent an SNA SIG
message. This normally indicates that the session partner wishes to
enter send state (you are expected to set
PREPARE–TO–RECEIVE–IND on a subsequent send verb when
convenient).