SNAX/HLS Management Programming Manual

SNAX/HLS Subsystem Command Descriptions
Commands and Responses
104708 Tandem Computers Incorporated 7–5
SNAX/HLS Subsystem
Command
Descriptions
On the following pages, each SNAX/HLS command and its response is described in
detail. The command descriptions appear in alphabetical order by command name.
Within each command description is a box that contains:
The symbolic name of the command number
The symbolic name of the object types that can be addressed in the command and
the object types that can be the target of the command
A list of tokens that can be present in the command buffer regardless of the object
type
A list of tokens that can be present in the response buffer regardless of the object
type
Additional tokens (those specific to an object type) are listed in a box where that object
type is discussed.
The order in which the tokens are presented in the command and response parts of the
syntax box is arbitrary, except that the token ZSPI–TKN–ENDLIST occurs after its
corresponding ZSPI–TKN–DATALIST, ZSPI–TKN–ERRLIST, or ZSPI–TKN–SEGLIST.
The notation used in the box for simple tokens is a shorthand version of the essential
information given in the DDL TOKEN–CODE statement. Extensible structured tokens
are defined by using DDL DEF statements.
For each token in the command buffer and each field of an extensible structured token
in the command buffer, the box contains an indication of whether the token or field
must be present in the command. For a token, the notation !r means the token is
required in the command, and the notation !o means the token is optional in the
command. For a field of an extensible structured token, the notation !r means the
field must have a value other than its null value, and the notation !o means the field
may or may not have a value other than its null value.
Following the box, the tokens for the command buffer and the tokens for the response
buffer are described in the same order as they appeared in the box.
Most of the SNAX/HLS attribute tokens are described in detail in Section 6, “Common
Definitions.” The Subsystem Programmatic Interface (ZSPI–) tokens are described in
the Distributed Systems Management (DSM) Programming Manual. The data
communications or ZCOM tokens and the ZCMK tokens are described in the
Communications Management Programming Manual.