EMS Manual

Collector Commands and Responses
EMS Manual—426909-005
19-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.

Optional signifies that the token is optional and need not be supplied by the user.

Ignored signifies that this token is tolerated in the command and ignored.
Common Command Token Descriptions
ZSPI-TKN-COMMAND
is the header token that contains the command number. Its value is of the form
ZCOM-CMD-command and is specified in the call to SSINIT.
ZSPI-TKN-OBJECT-TYPE
is the header token that contains the type of object to which the command is
applied. Its value is of the form ZCOM-OBJ-objtype and is specified in the call to
SSINIT.
ZSPI-TKN-SSID
is the header token that identifies the subsystem that processes the command.
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 not zero, the collector encapsulates
the response record in a data list (between the -DATALIST and the -ENDLIST
tokens). Multiple response records are supported. The default value for this token
is zero.
ZCOM-TKN-XMGR
is not required, but is allowed. More than one of these tokens is not allowed and
results in a ZCOM-ERR-TKN-DUP error.
ZCOM-TKN-REQID-PAID
ZCOM-TKN-REQID-PHANDLE
ZCOM-TKN-REQID-PPROGXFILE
ZCOM-TKN-REQID-PSTRING
are intended for security purposes and are not required. The EMS collectors use a
different method for validating the requestor. However, if these tokens are present
and the requestor has the proper security for the command, the contents of these
tokens are checked for proper security. If this second check fails, the command is
rejected with a ZCOM-ERR-SECURE-VIOL.