TCP/IP Management Programming Manual

Elements of SPI Messages
HP NonStop TCP/IP Management Programming Manual—529636-001
3-3
Naming Rules and Guidelines for Applications
An example of the definition files needed by a TCP/IP application written in C that
retrieves event messages is:
An example of the definition files needed by a TCP/IP application written in COBOL
that retrieves event messages is:
An example of the definition files needed by a TCP/IP application written in TACL that
retrieves event messages is:
These definition files are located on the disk volume chosen by your site. The default
disk volume used by the INSTALL program is $SYSTEM.
Section 5, Common Definitions, lists the SPI, EMS, and data communications standard
definitions used by the TCP/IP subsystem. For detailed descriptions of these standard
definitions, see the SPI Programming Manual, the EMS Manual, and the SPI Common
Extensions Manual, respectively. The declarations in the TCP/IP definition files are
described in Section 5, Common Definitions.
Naming Rules and Guidelines for Applications
All items in definition files are assigned symbolic names in addition to numbers. Use
the symbolic names to prevent transcription errors and to improve readability. HP uses
names beginning with the letter Z for all definitions and all component fields of
structures in its definition files. To avoid present and future conflicts with names defined
ZSPIDEF.ZSPIC SPI definitions
ZSPIDEF.ZEMSC EMS definitions
ZSPIDEF.ZCOMC Data communications definitions
ZSPIDEF.ZTCIC TCP/IP definitions
ZSPIDEF.ZSPICOB SPI definitions
ZSPIDEF.ZEMSCOB EMS definitions
ZSPIDEF.ZCOMCOB Data communications definitions
ZSPIDEF.ZTCICOB TCP/IP definitions
ZSPIDEF.ZSPITACL SPI definitions
ZSPIDEF.ZEMSTACL EMS definitions
ZSPIDEF.ZCOMTACL Data communications definitions
ZSPIDEF.ZTCITACL TCP/IP definitions
Note. This manual uses DDL to describe all tokens. For a brief explanation of DDL, refer to the
SPI Programming Manual. If you are programming in TAL or TACL, substitute a circumflex (^)
for each hyphen in a definition name as it appears in this manual. If you are programming in C,
substitute an underscore (_) for each hyphen in a definition name as it appears in this manual.
For example, ZCOM-OBJ-SUBNET becomes ZCOM^OBJ^SUBNET in TAL and TACL and
ZCOM_OBJ_SUBNET in C.