TCP/IP TELNET Management Programming Manual

GETVERSION Command

Commands and Responses

53474 Tandem Computers Incorporated 6–25

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. !...

ZSPI-TKN-SERVER-BANNER token-type ZSPI-TYP-CHAR50.!{}

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.

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 name of the TELNET process that is going to return the version

information. Your application must provide this token only if the value ZCOM-

OBJ-PROC has been specified. Your application cannot provide this token if the

value ZCOM-OBJ-NULL has been specified; the NULL object type does not have

an object name associated with it.

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 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.