SNAX/APC Management Programming Manual

STATUS LU
Commands and Responses
5–96 111813 Tandem Computers Incorporated
STATUS LU When the STATUS command is applied to the object type ZCOM-OBJ-LU, 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-ACTV-CONV-CNT token-type ZSPI-TYP-INT. !{}
ZAPC-TKN-ACTV-SESS-CNT token-type ZSPI-TYP-INT. !{}
ZAPC-TKN-SNAX-RETRY-COUNT token-type ZSPI-TYP-INT. !{}
ZAPC-TKN-TRACE-STATE token-type ZSPI-TYP-ENUM. !{}
ZAPC-TKN-TRACE-XFNAME token-type ZSPI-TYP-STRING. !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. SNAX/APC object names have the format
$ snax/apc-process-name . object-name . This token is required. Refer to
Section 3, “Elements of SPI Messages for SNAX/APC,” for further information on
object names.
ZAPC-TKN-ACTV-CONV-CNT
indicates the number of currently active conversations.
ZAPC-TKN-ACTV-SESS-CNT
indicates the currently active session count.
ZAPC-TKN-SNAX-RETRY-COUNT
indicates the number of retries of the open request that the local LU has
performed.
ZAPC-TKN-TRACE-STATE
indicates the current state of trace activity for the LU object.
ZAPC-TKN-TRACE-XFNAME
indicates the name of the file to which trace information is to be written. This
token may be returned only when the tracing is active.