OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual

Glossary
OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual—522223-001
Glossary-24
response message
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.
return token. In DSM programmatic interfaces, the token that indicates whether a command
was successful and, if not, why it failed. The token code for the return token is
ZSPI-TKN-RETCODE. Its value consists of a single integer field. See also error token.
root object. In the GPI, a message, probe, report, or P1-encoded object.
ROSE (Remote Operations Service Element). An Application Layer service definition and
protocol supporting interactive applications, implemented by the RS process in
OSI/MHS. Examples of ROSE PDUs are:
route. A path through an X.400 system from an originator to a recipient.
ROUTE object. An object type, used in OSI/MHS management interfaces, that defines
routing information to the OSI/MHS subsystem. You use the ROUTE object to define
and inquire about O/R names for addressing adjacent MTAs.
route retry. The action taken when an attempt to deliver a message to an adjacent MTA fails
after all links have been tried and exhausted. Route retry occurs when the subsystem
attempts to deliver the message by an alternate route.
route-selection criteria. The attributes that determine the route the message is to take.
routing. The selection of the adjacent MTA to which a message, probe, or report is
transferred.
routing database. A database in the OSI/MHS registration database that contains records of
ROUTE objects and APPL objects.
ROIV-APDU Invoke application protocol data unit
RORJ-PDU Reject application protocol data unit
ROER-APDU Error application protocol data unit
RORS-APDU Response application protocol data unit