SNAX/APC Management Programming Manual

STATUS SESS
Commands and Responses
5–102 111813 Tandem Computers Incorporated
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-MAP-FSM-STATES
is an extensible structured token that returns status information for the SESS
object. The tokens tagged with an asterisk (*) may have the value of 0 if the
session is not in the STARTED state. The tokens tagged with a cross (†) will have
the value of 0 if no conversation is active.
Refer to Section 4, “Common Definitions,” for further information about this
token.
ZAPC-TKN-CONV-ID
identifies the current conversation running in a session. This token is returned
only when there is an active conversation.
ZAPC-TKN-CUR-RCV-PACING-CNT
indicates the current number of request/response units (RUs) that SNAX/APC
can receive from the partner LU before the partner LU must wait for a pacing
response from the partner LU. If the session is not in the STARTED state, this
token might not be returned.
ZAPC-TKN-CUR-SEND-PACING-CNT
indicates the current number of request/response units (RUs) that SNAX/APC
can send to the partner LU before the SNAX/APC must wait for a pacing response
from SNAX/APC. If the session is not in the STARTED state, this token might not
be returned.
ZAPC-TKN-RCVD-BYTES-NOT-READ
indicates the number of bytes that have been received by the local LU but have not
yet been read by a transaction program (TP). If the session is not in the STARTED
state, this token might not be returned.