Expand Management Programming Manual

COMMANDS AND RESPONSES
Command Descriptions
COMMAND DESCRIPTIONS
On the following pages, each EXPAND command and its response
is described in detail. The command descriptions appear in
alphabetical order.
Within each command description, there is a box that contains the
symbolic name of the command number, the symbolic names of all
object types accepted by the command, a list of tokens that can
be present in the command buffer, and a list of tokens that can
be present in the response buffer.
The order in which tokens are presented in the command and
response parts of the syntax box is arbitrary, except that ZSPI-
TKN-ENDLIST occurs after its corresponding ZSPI-TKN-DATALIST or
ZSPI-TKN-ERRLIST. The syntax box shows the pairs ZSPI-TKN-
DATALIST ... ZSPI-TKN-ENDLIST and ZSPI-TKN-ERRLIST ... ZSPI-
TKN-ENDLIST together to show that they are pairs. In the actual
buffer, both sets of pairs enclose additional tokens.
In the actual buffer, the token ZSPI-TKN-DATALIST, if present,
always appears at the beginning of each response record, and
the token ZSPI-TKN-ENDLIST always appears at the end of each
response record. The other tokens listed in the response part
of the syntax box, except for the context token ZSPI-TKN-CONTEXT,
are the tokens that can be contained in a response record.
Similarly, in the buffer, each ZSPI-TKN-ERRLIST ... ZSPI-TKN-
ENDLIST pair encloses a set of tokens; this set of tokens depends
not on the command but on the value of ZSPI-TKN-RETCODE, and are
given in Appendix A.
For more information on the structure of responses, and for
information on the context token, refer to the Distributed
Systems Management (DSM) Programming Manual .
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 for each field of
an extensible structured token in the command buffer, the box
contains an indication of whether or not the token or field must
be present in the command. For a token, the notation "!r" means
that the token must be present (is required) in the command, and
the notation "!o" means that the token may or may not be present
(is optional) in the command. For a field of an extensible
structured token, the notation "!r" means that the field must
have a value other than its null value, and the notation "!o"
means that the field may or may not have a value other than its
null value.
7-5