SNAX/APC Management Programming Manual

ADD Command
Commands and Responses
5–14 111813 Tandem Computers Incorporated
Tokens in Command Buffer
ZSPI-TKN-MANAGER
is a standard SPI token that is optional for SNAX/APC. In other subsystems, this
token contains the process name; however, for SNAX/APC, object names include
the SNAX/APC process name, so this token is not necessary.
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 required. Refer to
Section 3, “Elements of SPI Messages for SNAX/APC,” and Section 4, “Common
Definitions,” for further information on object names.
ZCOM-TKN-CMD-TIMEOUT
is a standard data communications token described in the SPI Common Extensions
Manual.
(ZSPI-TKN-)MAXRESP, CONTEXT, and ALLOW-TYPE
are standard SPI tokens described in the SPI Programming Manual.
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-ADD, the valid object types are LU, PTNR-LU, PTNR-MODE, SESS,
and TPN.
ZSPI-TKN-RETCODE
indicates whether the command was successful and, if not, the reason for failure.