SNAX/APC Management Programming Manual

STATUS CONVERSATION
Commands and Responses
111813 Tandem Computers Incorporated 5–95
STATUS CONVERSATION When the STATUS command is applied to the object type ZCOM-OBJ-
CONVERSATION, the following additional tokens are involved.
Tokens in Command Buffer
(no additional tokens)
Tokens in Response Buffer
ZCOM-TKN-OBJSTATE token-type ZSPI-TYP-ENUM. !{}
ZAPC-TKN-FSM-CONV token-type ZSPI-TYP-ENUM. !{}
ZAPC-TKN-RCVD-BYTES-NOT READ token-type ZSPI-TYP-INT.!see text
ZAPC-TKN-RUS-TO-BE-SENT token-type ZSPI-TYP-INT.!see text
ZAPC-TKN-SESS-ID token-type ZSPI-TYP-STRING.!see text
ZAPC-TKN-VERB-IN-PROGRESS token-type ZSPI-TYP-ENUM.!see text
Tokens in Response Buffer
Refer to Section 4, “Common Definitions,” for more information on the following
tokens.
ZCOM-TKN-OBJSTATE
is a standard data communications token that identifies the object name and the
SNAX/APC process name.
ZAPC-TKN-FSM-CONV
indicates the conversation status. The possible values are listed in Section 4,
“Common Definitions.”
ZAPC-TKN-RCVD-BYTES-NOT-READ
specifies the number of bytes that have been received by the local LU but have not
yet been read by a transaction program (TP). This token is returned only when the
session is not freed.
ZAPC-TKN-RUS-TO-BE-SENT
indicates the number of RUs waiting to be sent to the partner LU.
ZAPC–TKN–SESS-ID
indicates the session on which this conversation is running. This token may not
exist if the session has just been lost. This token is returned only when the session
is not freed.
ZAPC-TKN-VERB-IN-PROGRESS
indicates the verb that SNAX/APC is processing for the conversation on this
session. This token is returned only when there is an outstanding verb.