Naming Conventions; Contents - HP NonStop Pathway/iTS Programming Manual

SPI Programming Considerations
SPI and EMS) also provide definition files. Each software component includes
definition files for the TAL, COBOL, TACL, C, PASCAL, and DDL languages.
To use the data declarations defined by a particular NonStop software component,
your application must incorporate the appropriate programming-language definition file
associated with that software component. The declarations in a COBOL definition file
are grouped into sections to enable COBOL programs to declare multiple copies of
structures in the definition file. TAL programs can use as a source either the entire
definition file or just the sections they require. The TACL command interpreter always
loads the entire definition file. For further information about how definition files are used
by an application, see the SPI Programming Manual.

Naming Conventions

Definition files are named according to the following convention:
ZSPIDEF.ZsubsysC
ZSPIDEF.ZsubsysCOB
ZSPIDEF.ZsubsysDDL
ZSPIDEF.ZsubsysPAS
ZSPIDEF.ZsubsysTACL
ZSPIDEF.ZsubsysTAL
subsys
is a three-character code identifying the subsystem or other software component to
which these definitions belong. The code for the Pathway subsystem is PWY.
The last characters of each file name denote the language in which the definitions in
this file are coded.

Contents

The Pathway definition files contain the following definitions:
Object names for use in error tokens and object-selector tokens
Error tokens
Attribute (DEF-) tokens
Command-modifier (PAR-) tokens
Object-selector (SEL-) tokens
Qualifier (QUAL-) tokens
Commands
Object types
Token types, used in defining simple tokens
NonStop Pathway/iTS Management Programming Manual—426749-002
3 -2
Naming Conventions