Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
Desktops - HP Integrity NonStop H-Series (1.98 mb)
Desktops - HP Integrity NonStop H-Series (16.73 mb)
Desktops - HP Integrity NonStop H-Series (957.56 kb)
Desktops - HP Integrity NonStop H-Series (2.38 mb)
Desktops - HP Integrity NonStop H-Series (881.66 kb)
Desktops - HP Integrity NonStop H-Series (965.62 kb)
Desktops - HP Integrity NonStop H-Series (676.93 kb)
Desktops - HP Integrity NonStop H-Series (393.72 kb)
Desktops - HP Integrity NonStop H-Series (776.57 kb)
manual abstract
Glossary
content
content. One of two basic parts of a message or report, containing the information to be
conveyed to the recipients. The other part is called the “envelope.” Probes contain a
description of the content rather than the content itself.
context token. In DSM programmatic interfaces, a token in an SPI response message that
indicates (by its presence or absence) whether or not the response is continued in the
following message.
control and inquiry. In DSM, those operations that affect or request information about the
state or configuration of an object. See also event management.
correspondent. A sender or receiver of information within the Transfer subsystem.
Examples of possible types of correspondents are a person, an interest group, a process,
or a device.
criticality. An X.400 mechanism related to extensions. Criticality indicates whether or not
an extension must be understood by an application. A noncritical extension may be
ignored or discarded by the application. A critical extension must be acted upon. For
X.400, three types of criticality are defined: critical-for-delivery, critical-for-
submission, and critical-for-transfer.
critical-for-delivery. In X.400, a type of criticality. Critical-for-delivery means an extension
is critical for delivery of a message. If critical-for-delivery is indicated, the extension
must be understood and processed by the MTS component that would perform the
message delivery; for example, the final MTA. If the MTS component does not handle
that extension, a nondelivery report is generated and the message is discarded. If
critical-for-delivery is not indicated, and the message is sent to an MTS component that
cannot accept the extension (for example, a 1984 gateway), the extension is deleted and
the message is delivered.
critical-for-submission. In X.400, a type of criticality. Critical-for-submission means an
extension is critical for submission of a message. If critical-for-submission is indicated,
the extension must be understood and processed by the MTS component that would
accept the submission; for example, the originating MTA. If the MTS component does
not handle that extension, the message submission is rejected.
critical-for-transfer. In X.400, a type of criticality. Critical-for-transfer means an extension
is critical for transfer of the message. If critical-for-transfer is indicated, the extension
must be understood and processed by the MTS component that would perform the
transfer, usually an MTA. If the MTS component does not handle that extension, the
message is stored or discarded and a nondelivery report is returned.
critical event. A DSM event that is crucial to the operation of the system or network. Each
subsystem determines which of its events are critical, designating them as such by
setting the value of the emphasis token to TRUE. See also noncritical event.
CUG (closed user group). A set of users who may communicate with one another. Closed
user groups are an optional feature of OSI/MHS and are not part of the X.400
recommendations; when CUGs are established, users may communicate with one
another only if both are part of the same CUG.
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide —424822-001
Glossary- 5
...Other models in this manual:
Desktops - HP Integrity NonStop J-Series (758.59 kb)
Desktops - HP NonStop G-Series (758.59 kb)
Desktops - HP NonStop L-Series (758.59 kb)