COMMANDS AND RESPONSES
DELETE Command
ZSPI-TKN-MAXRESP token-type ZSPI-TYP-INT.
ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING.
ZSPI-TKN-RESPONSE-TYPE token-type ZSPI-TYP-ENUM.
ZSPI-TKN-ALLOW-TYPE token-type ZSPI-TYP-ENUM.
ZSPI-TKN-COMMENT token-type ZSPI-TYP-STRING.
Tokens in Response Buffer
ZSPI-TKN-SERVER-VERSION token-type ZSPI-TYP-INT. !{}
ZSPI-TKN-SSID token-type ZSPI-TYP-SSID. !{}
ZSPI-TKN-DATALIST token-type ZSPI-TYP-LIST. !...
ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !{}
ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM. !{}
ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. !...
...
ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
ZSPI-TKN-RETCODE token-type ZSPI-TYP-ENUM. !{}
ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING.
Tokens in Command Buffer
ZCOM-TKN-OBJNAME specifies either the line whose subdevices are
to be deleted or the subdevice that is to be deleted. Your
application must provide this token in the command. This
token is described in "Data-Communications Standard Definitions"
in Section 5, "Common Definitions," and the
Communications
Management Programming Manual.
ZCOM-MAP-REQID and ZCOM-TKN-CMD-TIMEOUT are standard data-
communications tokens that your application can optionally pro-
vide. These tokens are described in "Data-Communications
Standard Definitions" in Section 5 and the
Communications
Management Programming Manual.
(ZSPI-TKN-) MANAGER, SSID, MAXRESP, RESPONSE-TYPE, ALLOW-TYPE,
and COMMENT are standard SPI tokens. With the exception of the
ZSPI-TKN-SSID token, which your management application must pass
to SSINIT, these tokens are optional. These tokens are described
in "SPI Standard Definitions" in Section 5 and the
Distributed
Systems Management (DSM) Programming Manual.
6-37