Expand Management Programming Manual

ELEMENTS OF SPI MESSAGES FOR THE EXPAND SUBSYSTEM
Other Tokens
A table of all the token codes defined by the EXPAND subsystem
(token codes with names of the form ZEXP-TKN- name ) can be found
in Appendix B.
Token Types
The token types used by the EXPAND subsystem are represented
by symbolic names of the form subsys -TYP- name , where subsys
is a four-character subsystem abbreviation and name identifies
the token type. For example, the token type ZSPI-TYP-CHAR8
represents a string of eight ASCII characters. The EXPAND
subsystem does not define any private token types; that is, no
token types have names of the form ZEXP-TYP- name .
Throughout this manual, when a simple token is described, its
token type is given.
Predefined Value Names
The predefined values used by the EXPAND subsystem are repre-
sented by symbolic names of the form subsys -VAL- name , where
subsys is a four-character subsystem abbreviation and name
identifies the predefined value. For example, the predefined
value ZEXP-VAL-RS232 represents the RS-232 hardware interface.
Extensible Structured Tokens
Extensible structured tokens--tokens whose values are extensible
structures--are identified by token maps. The token maps for
the extensible structured tokens used by the EXPAND subsystem
are represented by symbolic names of the form subsys -MAP- name ,
where subsys is a four-character subsystem abbreviation and name
identifies the token map. For example, the token map ZEXP-
MAP-STATS-PATH identifies an extensible structured token that
contains all the statistical information for one path.
All EXPAND commands can contain extensible structured tokens.
The responses to the following EXPAND commands can also contain
extensible structured tokens:
INFO STATISTICS
PROBE STATUS
RESETSTATS
4-6