AM3270 Management Programming Manual
 COMMANDS AND RESPONSES
 DISCONNECT Command
 (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
.
 Tokens in Response Buffer
 ZSPI-TKN-SSID is an echo of the subsystem ID value provided
 by your application. This token is described in "SPI Standard
 Definitions" in Section 5, "Common Definitions," and the
Distributed Systems Management (DSM) Programming Manual
.
 ZSPI-TKN-SERVER-VERSION indicates the software release version of
 the AM3270 subsystem. This token is described in "SPI Standard
 Definitions" in Section 5 and the 
Distributed Systems Management
(DSM) Programming Manual
.
 ZSPI-TKN-DATALIST indicates the beginning of a data list. This
 token is described in "SPI Standard Definitions" in Section 5 and
 the 
Distributed Systems Management (DSM) Programming Manual
.
 ZCOM-TKN-OBJNAME specifies the name of the AM3270 subdevice that
 was trying to delete the link to the TR3271 subdevice. Unless
 there is an error that prevents the DISCONNECT command from being
 attempted at all, this token is present in every response record.
 ZCOM-TKN-OBJNAME is described in "Data-Communications Standard
 Definitions" in Section 5 and the 
Communications Management
Programming Manual
.
 ZCOM-TKN-OBJTYPE specifies the type of AM3270 object that at-
 tempted to delete the link. The only valid value for this
 token is ZCOM-OBJ-SU (SU object) This token is described in
 "Data-Communications Standard Definitions" in Section 5, "Common
 Definitions," and the 
Communications Management Programming
Manual
.
 ZSPI-TKN-ERRLIST indicates the beginning of an error list.
 Within the error list, the object experiencing the error is
 listed. This token is described in "SPI Standard Definitions"
 in Section 5 and the 
Distributed Systems Management (DSM)
Programming Manual
.
 6-44










