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

Glossary
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
Glossary-7
element
element. See string element.
element of service. In OSI, a feature or function defined as part of a service.
empty response record. In DSM programmatic interfaces, a response record containing only
a return token with a value that means “no more response records.”
EMS (Event Management Service). A part of DSM used to provide event collection, event
logging, and event distribution facilities. It provides for different event descriptions for
interactive and programmatic interfaces, lets an operator or application select specific
event-message data, and allows flexible distribution of event messages within a system
or network. EMS has SPI-based programmatic interfaces for reporting events and
retrieving event messages.
EMS collector. See collector.
EMS standard definitions. The set of declarations provided by EMS for use in event
management, regardless of the subsystem. Any application that retrieves tokens from
event messages needs the EMS standard definitions. See also definition files, data
communications standard definitions, or SPI standard definitions.
encoding. The process of translating local message information into ASN.1 (BER) format.
See also decoding and BER.
entry manager process. A queue manager process that you must specify when configuring
the Transfer X400 gateway. You can specify up to five entry manager processes.
envelope. The part of a message that contains information needed to transfer the message and
to deliver it to its intended recipients. The envelope takes different forms from the time
the message is submitted to the time it is delivered or retrieved, and depending on
whether it is submitted or retrieved directly through an MTA or through a message store.
See also content.
error. A condition that causes a command or other operation to fail. See also warning.
error list. In DSM programmatic interfaces, a group of tokens used within a response record
to provide error and warning information. An error list consists of a list token that
denotes an error list (different from the token that starts a data list or a generic list),
followed by an error token, other tokens explaining the error (optional), and an end-list
token. Error lists can be nested within other error lists. The return token cannot be
included in an error list.
error number. In DSM programmatic interfaces, a value that can be assigned to a return
token, or to the last field of an error token, to identify an error that occurred. Some error
numbers are defined in the data communications (ZCOM) definitions; others are defined
by individual subsystems.
error token. In DSM programmatic interfaces, a token in a response message that indicates
the reason an error occurred in performing a programmatic command. Compaq
subsystems enclose each error token in an error list, which can also contain additional