TCP/IP TELNET Management Programming Manual

ABORT Command
Commands and Responses
6–6 53474 Tandem Computers Incorporated
Tokens in Response Buffer
ZSPI-TKN-SSID token-type ZSPI-TYP-SSID. !{}
ZSPI-TKN-SERVER-VERSION token-type ZSPI-TYP-UINT. !{}
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-RETCODE token-type ZSPI-TYP-ENUM. !{}
ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST. !...
...
ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING.
Tokens in Command Buffer
ZSPI-TKN-SSID
identifies the subsystem ID. Your application must provide this token in the
command. The value for the TELNET subsystem is ZTNT-VAL-SSID. This token
is described more fully in “SPI Standard Definitions” in Section 5, “Common
Definitions.”
ZCOM-TKN-OBJNAME
specifies the window that is going to be terminated. Your application must
provide this token in the command. The object name can include wild-card
characters. If wild-card characters are used, the command can affect multiple
windows. This token is described more fully in “Data Communications Standard
Definitions” in Section 5.
ZCOM-MAP-REQID
is a standard data communications token your application can optionally provide.
This token is described in “Data Communications Standard Definitions” in
Section 5.
(ZSPI-TKN-) MAXRESP, CONTEXT, ALLOW-TYPE, and COMMENT
are standard SPI tokens your application can optionally provide. These tokens are
described in “SPI Standard Definitions” in Section 5.
Tokens in Response Buffer
ZSPI-TKN-SSID
identifies the subsystem ID. The value for the TELNET subsystem is ZTNT-VAL-
SSID. This token is described more fully in “SPI Standard Definitions” in
Section 5.