OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

Glossary
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
Glossary-24
recipient
recipient. A person or application that receives a message from a message handling system.
registration database. An OSI/MHS database that consists of three files: APPL, route, and
adjacent MTA.
reliable transfer service. See RTSE.
remote MTA. An adjacent or nonadjacent MTA. Any MTA other than your local OSI/MHS
subsystem.
Remote Operations Service. See ROSE.
remote system. In Compaq terms, any system within an Expand network that is not the local
system.
remote user agent. See RUA.
report. A notification generated by the OSI/MHS subsystem that tells the user whether the
message has been sent.
request primitive. In OSI, a primitive issued when a service user wants the service to do
some work. This is one of four types of service primitives. See also service primitive.
reserved object. An object on the input queue that the client program has started transferring
in and to which the GPI has assigned an object identifier. A client program can examine
or copy a reserved object (and its attributes) but not modify it.
response. In OSI, see response primitive.
In DSM, the information or confirmation supplied (as part of a response message) to an
application by a subsystem in reaction to a DSM command.
response message. An SPI message sent from a subsystem to an application program in
reaction to a command message. See also command message or event message.
response primitive. In OSI, a primitive issued when a service user wants to respond to an
event. This is one of the four types of service primitives and is used only for confirmed
services. See also service primitive.
response record. In DSM programmatic interfaces, a set of response tokens, usually
describing the results of performing a command on one object. Every response record in
a response from a Compaq subsystem contains a return token; a response record can also
contain error lists that include error tokens. A response can consist of multiple response
records, spread across one or more response messages.
result file. In the P7 API, a file used for retrieving results from the OSI/MHS subsystem. The
file number is returned by a call to the LOS_OPEN_ procedure. See also send file.