SNAX/APC Management Programming Manual

ABORT Command
Commands and Responses
5–10 111813 Tandem Computers Incorporated
Tokens in Response Buffer
ZSPI-TKN-DATALIST
is a standard SPI data list, as described in the SPI Programming Manual. The list
ends with the token ZSPI-TKN-ENDLIST.
ZCOM-TKN-OBJNAME
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 always present in the
response buffer. Refer to Section 3, “Elements of SPI Messages for SNAX/APC,”
and Section 4, “Common Definitions,” for further information on object names.
ZCOM-TKN-OBJTYPE
is a standard data communications token that indicates the object type. For
ZCOM-CMD-ABORT, the valid object types are LU, PTNR-LU, PTNR-MODE,
SESS, TPN, and TPI.
ZSPI-TKN-RETCODE
indicates whether the command was successful and, if not, the reason for failure.
ZSPI-TKN-ERRLIST
is a standard SPI error list, as described in the SPI Programming Manual. The list
ends with the token ZSPI-TKN-ENDLIST.
ZSPI-TKN-CONTEXT
is the standard SPI context token, discussed in the SPI Programming Manual.
Operational Notes
An object can be aborted while it is still in the STARTING state, except for the
PTNR-MODE object when it is waiting for its CNOS
(INITIALIZE_SESSION_LIMIT) response from its partner LU.
The ABORT LU command shuts down the local LU entirely and closes its
underlying access method. As a result, the local LU can no longer accept any
conversation verbs from transaction programs, and will not accept any SNA
commands from its partner LUs.
The ZAPC-TKN-SNAX-RETRY-COUNT token on the INFO LU command is reset
to 0 after the target LU is aborted.
After the specified PTNR-LU object is aborted, the local LU can no longer initiate
sessions with the partner LU. In a similar manner, BIND requests received from
the partner LU are rejected.