OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual

Glossary
OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual522223-001
Glossary-4
command file
command file. An EDIT file that contains sequences of commands. Sometimes called an
OBEY file.
command message. An SPI message, containing a command, sent from an application
program to a subsystem. See also response message or event message.
command/response interface. In DSM, a management interface that performs operations on
subsystem-defined objects.
common definition. In DSM programmatic interfaces, a definition (data declaration) used in
several commands, responses, or event messages in an SPI interface to a subsystem.
communication. The transfer of information between or among different entities, or the
information transmitted. In GPI manuals, this term is used to designate a message, a
probe, or a report in statements that apply to all three of these types of X.400 messages.
compatibility distributor. An EMS distributor process that filters event messages according
to fixed (rather than user-specified) criteria, obtains text for these messages that is
compatible with the operator console of Guardian 90 operating system versions earlier
than C00, and writes the text to the standard Guardian 90 console-message destinations.
conditional token. In DSM event management, a token that is sometimes, but not always,
present in a particular event message. See also unconditional token.
configuration and control components. The OSI/MHS components (such as the MHS
manager and configuration databases) and related products (such as SCF) that
specifically support management of the OSI/MHS subsystem.
configuration database. An OSI/MHS database that consists of the following databases:
subsystem, class, group, process, local MTA and MTA identity, entry, OSI address, MS
configuration, and RTS configuration.
configuration database subvolume. The subvolume that contains the OSI/MHS
configuration database. The default location is the same subvolume as the executable
object file for the MHS manager process This subvolume contains a set of Enscribe
files. The files are protected by TMF auditing. The file names are prefixed with the
first four characters of the process name of the MHS manager.
configuration file. An SCF command file that contains all the configuration information
about one subsystem. See also OSI/MHS subsystem.
configured object. An object whose characteristics have been defined to OSI/MHS through
SCF or a management application. See also nonconfigured object.
confirm primitive. In OSI, a primitive issued when a service user is to be informed about its
request. This is one of four types of service primitives. See also service primitive.
connection. In OSI, a relationship between a service access point on one protocol stack and a
corresponding point on a different protocol stack in the desired system (this could be the
same system, or another local or remote system). See also association.