EMS Manual

Distributor Commands and Responses
EMS Manual—426909-005
17-6
Common Command Tokens for ZCOM- Commands

Basic SPI signifies that the presence of this token in the command is dictated by
the basic SPI command language standards that govern multiple objects and
responses. The distributor is not extended SPI-compliant in this regard: if multiple
object instances are returned, and MAXRESP is not equal to zero, all responses
are framed by one data list, The EMS collector, by comparison, puts each
response (object instance) in a separate data list.

Required signifies that the token is required and must be supplied by the user.
Common Command Token Descriptions
ZSPI-TKN-COMMAND
contains the command number. Its value is of the form ZCOM-CMD-command and
is specified in the call to SSINIT.
The header token can have these values for the distributor’s extended
programmatic interface commands:
ZCOM-CMD-ADD 5005
ZCOM-CMD-ALTER 5003
ZCOM-CMD-DELETE 5007
ZCOM-CMD-STATUS 8
ZEMS-CMD-REPLACE 30000
ZSPI-TKN-OBJECT-TYPE
contains the type of object to which the command is applied. Its value is of the form
ZCOM-OJB-objtype and is specified in the call to SSINIT. These object types are
supported:
ZCOM-OBJ-DIST 70
ZCOM-OJB-FILTER 75
ZCOM-OBJ-SOURCE 72
ZCOM-OBJ-TARGET 74
ZCOM-OBJ-TEXTOUT 73
ZSPI-TKN-SSID
identifies the subsystem that processes the command. In the ZCOM- distributor
commands, this subsystem is always defined as ZSPI-VAL-TANDEM.ZSPI-SSN-
ZEMS.ZEMS-VAL-VERSION. This value is specified in the call to SSINIT.
ZSPI-TKN-MAXRESP
if the value of this command header token is nonzero, the distributor encapsulates
the response in a data list (that is, between the -DATALIST and the -ENDLIST
tokens). If multiple object instances occur, they are all enclosed in the same data
list. By comparison, the collector encapsulates each object instance (response) in
its own data list to be compliant with the SPI common extensions interface
standards.