SNAX/APC Management Programming Manual

INFO TPI
Commands and Responses
5–62 111813 Tandem Computers Incorporated
INFO TPI When the INFO command is applied to the object type ZCOM-OBJ-TPI, the following
additional tokens are involved.
Tokens in Command Buffer
(no additional tokens)
Tokens in Response Buffer
ZAPC-TKN-DISPATCHED-IND token-type ZSPI-TYP-BOOLEAN. !{}
ZAPC-TKN-LOCAL-ATTACH-IND token-type ZSPI-TYP-BOOLEAN. !{}
ZAPC-TKN-LOCAL-TP-PROC-NAME token-type ZSPI-TYP-STRING. !{}
ZAPC-TKN-RESOURCE-ID type ZSPI-TYP-STRING.!see text
ZAPC-TKN-TPI-ORIGIN token-type ZSPI-TYP-ENUM. !{}
Tokens in Response Buffer
Refer to Section 4, “Common Definitions,” for a detailed description of these tokens.
ZAPC–TKN-DISPATCHED-IND
indicates if the TP-READY request is initiated by a DISPATCH-TP request.
ZAPC–TKN-LOCAL-ATTACH-IND
indicates if this transaction program instance was created by the local SNAX/APC
process sending or receiving the Attach request. If it was created due to the
sending of an Attach request, the value is true, but if it was created due to the
receiving of an Attach request, the value is false.
ZAPC–TKN–LOCAL-TP-PROC-NAME
indicates the file name of the local TPN of which this TPI is an instance.
ZAPC–TKN-RESOURCE-ID
displays in hexadecimal digits the identifier used by SNAX/APC to identify the
conversation and its resources. This token may not exist if this TPI is still in the
STARTING state and the ZAPC-TKN-TPI-ORIGIN token value is ZAPC-VAL-TPI-
ORIGIN-REMOTE.
ZAPC–TKN-TPI-ORIGIN
indicates where the TPI originated: at the local LU or the remote LU.