OSI/MHS P7 Application Programmatic Interface (P7 API) Manual

Glossary
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
Glossary-18
OSI/MHS database
The Compaq implementation of an X.400 message handling system for Compaq
NonStop systems.
OSI/MHS database. The database that consists of the registration database and OSI/MHS
configuration database.
OSI/MHS ISV. The installation subvolume for the OSI/MHS release. The Install process
creates this subvolume as ZOSIMHS.
OSI/MHS subsystem. The set of all processes and files defined through the installation
procedure, and through SCF or management applications, to be part of an OSI/MHS
environment, under control of a specified MHS manager. There can be more than one
OSI/MHS subsystem on a Compaq NonStop system.
OSI/MHS subvolume. The subvolume that contains all files required by an OSI/MHS
subsystem, such as executable object and configuration files. The MHS manager must
always reside in this subvolume, but some of the other executable files can reside
elsewhere, as defined by the MHS manager.
OSI Reference Model. A communications architecture, adopted by the ISO in 1984, that
includes seven layers that define the functions involved in communications between two
systems, the services required to perform these functions, and the protocols associated
with these services. See also layer.
OSI services. The Compaq implementation of the OSI Reference Model. OSI services
consist of an OSI manager process and a number of subordinate protocol processes. The
protocol processes handle OSI protocols and provide layer services. The network
service provider, NSP, handles layers 1 through 3 and is provided by access methods
such as X25AM and TLAM. The transport service provider, TSP, handles Layer 4 and
is provided by OSI/TS. The TSP process also provides Layer 3 for LANs. The session,
presentation, and application services provider, TAPS, handles layers 5, 6, and 7, and is
provided by OSI/AS.
outbound communication. A communication sent to the X.400 network from a client. See
also inbound communication.
output queue. A queue for messages, probes, and reports that are outbound from the gateway
application to X.400.
P1 protocol. The X.400 message transfer protocol, which defines the transfer of messages
between two message transfer agents (MTAs).
P1 message. An X.400 message that consists of an envelope and its content. The envelope
contains delivery information; the content is the actual information that is to be
delivered to the recipient.
P2 protocol. The X.400 interpersonal message (IPM) user agent protocol, which defines the
format by which one user agent (UA) sends an interpersonal message (IPM) to one or
more other UAs.