OSI/TS Management Programming Manual

4 Common Definitions
056786 Tandem Computers Incorporated 4–1
This section lists the common definitions—those used in several commands,
responses, or event messages—for the OSI/TS subsystem. Definitions used in only
one or two commands, responses, or event messages are described along with that
individual command or event message in Section 5 or Section 6, respectively. Sections
5 and 6 also provide any additional considerations for the common definitions as they
apply to the particular command or event message being described.
Common definitions used in OSI/TS commands, responses, and event messages fall
into six categories, based on their source:
SPI standard definitions
Data communications standard definitions
EMS standard definitions (for event messages only)
Guardian 90 definitions
File-system definitions
OSI/TS definitions
This section lists the definitions used in the interface to OSI/TS and provides
considerations, if any, specific to their use with OSI/TS. For full descriptions of these
definitions, refer to the following manuals:
Distributed Systems Management (DSM) Programming Manual, for SPI definitions
Event Management Service (EMS) Manual, for EMS definitions
Communications Management Programming Manual, for data communications
definitions
System Procedure Errors and Messages Manual, for Guardian 90 and file-system
definitions
Tandem provides each set of definitions in several programming languages, as
described under “Definition Files” in Section 3. Tandem also provides the Data
Definition Language (DDL) source file from which the definitions (data declarations)
in other languages are derived. Wherever it is necessary to show the type or structure
represented by a definition discussed in this section, its DDL definition is shown as it
appears in the appropriate DDL definition file. Fixed and extensible structures are
defined by using DDL DEF statements. For an explanation of DDL as it applies to SPI,
refer to the appendix “Overview of DDL for SPI” in the Distributed Systems
Management (DSM) Programming Manual.
Note As explained in Section 3 under “Naming Guidelines,” tokens that start with a ZX____ are for D-series
systems only. They are either new tokens or a replacement for a token similarly named (but without the
"X") for C-series systems. Information will be returned in the D-series token and also in the C-series
equivalent if the information fits (the field is otherwise left null).