OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

Glossary
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
Glossary-6
CUG object
CUG object. An object type, used in OSI/MHS management interfaces, that identifies a
closed user group to the Compaq OSI/MHS subsystem.
CUGMEMBER object. An object type, used in OSI/MHS management interfaces, that
identifies an individual member of a closed user group.
data communications standard definitions. In DSM, the set of declarations provided by
Compaq for use in all management applications that manage or retrieve event messages
from Compaq data communications subsystems. The names of these definitions start
with either ZCOM or ZCMK. See also definition files, SPI standard definitions, or EMS
standard definitions.
Data Link Layer. Layer 2 in the OSI Reference Model. This layer packages data for
transmission across the physical link and ensures that the data arrives at the next layer
without any errors.
data list. In DSM programmatic interfaces, a group of tokens used to separate response
records within an SPI message for a response, or to enclose a single response record, if
the program so requests. A data list consists of a list token that denotes a data list
(different from the token that starts an error list or a generic list), followed by a response
record and an end-list token.
decoding. The process of changing ASN.1 encoded (BER) data into a local representation.
See also encoding and BER.
definition. A declaration provided by Compaq for use in applications that use a specific
procedural interface, such as the APS or SPI procedures. Definitions are commonly
provided in definition files.
definition files. A set of files containing declarations for use in applications that use a
specific procedural interface.
In the case of the Subsystem Programmatic Interface (SPI), there is a standard definition
file in Data Definition Language (DDL) and a definition file for each of the
programming languages supporting SPI; the latter files are derived from the DDL
definition file. Likewise, each subsystem that has a token-oriented programmatic
interface has one definition file for DDL and one for each programming language.
Some subsystems—for instance, data communications subsystems—have additional,
shared definition files. See also SPI standard definitions, data communications standard
definitions, or EMS standard definitions.
delivery envelope. An “inner” X.400 envelope that relates to the P3 protocol. A delivery
envelope may be included in the message body part for an IPM or the primary body part
for an EDI interchange. A delivery envelope is not the same as and should not be
confused with an “outer” X.400 envelope, which is attached to messages, probes, and
reports and relates to the P1 protocol.
delivery report. A notification to the originator of a message that indicates the message was
successfully delivered to each of the intended recipients. See also nondelivery report.