TCP/IP Management Programming Manual

Elements of SPI Messages
HP NonStop TCP/IP Management Programming Manual—529636-001
3-9
Constructs Involving Multiple Tokens
value names. For more information on the form of these predefined value names, see
Predefined Value Names on page 3-9. Note that extensible structured tokens do not
appear in any event message issued by the TCP/IP subsystem.
For more information on all the token maps defined by the TCP/IP subsystem, see
Section 5, Common Definitions.
Token Types
The token types used by the TCP/IP subsystem are represented by symbolic names of
the form Zsubsys-TYP-name, where subsys is a three-character subsystem
abbreviation and name identifies the token type.
For more information on all the token types used by the TCP/IP subsystem, see
Section 5, Common Definitions.
Predefined Value Names
The predefined value names used by the TCP/IP subsystem are represented by
symbolic names of the form Zsubsys-VAL-name, where subsys is a three-character
subsystem abbreviation and name identifies the predefined value. For example, the
predefined value ZTCI-VAL-SSID represents the subsystem ID of the TCP/IP
subsystem that is present in all commands and responses associated with the TCP/IP
subsystem. For more information on all the predefined value names used by the
TCP/IP subsystem, see Section 5, Common Definitions.
Field Types
The field types used by the TCP/IP subsystem are represented by symbolic names of
the form Zsubsys-DDL-ftype, where subsys is a three-character subsystem
abbreviation and ftype identifies the field type. For example, the field type
ZSPI-DDL-BOOLEAN represents the Boolean data type. Although most field types are
defined by SPI, private field types can be defined by a subsystem. The TCP/IP
subsystem does not define any private field types. For more information on all the field
types used by the TCP/IP subsystem, see Section 5, Common Definitions.
Constructs Involving Multiple Tokens
The TCP/IP subsystem supports two kinds of constructs that involve multiple tokens:
data lists and error lists. For the TCP/IP subsystem, these constructs are found only in
a response buffer from the subsystem. A data list begins with the token
ZSPI-TKN-DATALIST, while an error list begins with the token ZSPI-TKN-ERRLIST;
both end with the token ZSPI-TKN-ENDLIST.
A data list is used in a response buffer to enclose information about one object or, in
some cases, a related group of objects.
An error list is used in a response buffer to enclose information about an error or
warning.