OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-43
ENTRY Objects
If a message is placed on the route-retry queue more than once, the delay increases
as specified by the appropriate CLASS attribute from this list (depending on the
category of message):
URGENT-ROUTE-RETRY-GROW
NORMAL-ROUTE-RETRY-GROW
NONURGENT-ROUTE-RETRY-GROW
REPORT-ROUTE-RETRY-GROW
The delay time increases exponentially with each retry, according to the following
formula:
delay =xxx-ROUTE-RETRY-DELAY *
(1.0 + xxx-ROUTE-RETRY-GROW/100) ^ attempts
where ^ means “to the power of,” and attempts means the number of times the
message has been on the route-retry queue (including the current time).
The following CLASS attributes determine how long a message can exist in the X.400
domain before it must be delivered:
URGENT-ROUTE-RETRY-TIME
NORMAL-ROUTE-RETRY-TIME
NONURGENT-ROUTE-RETRY-TIME
REPORT-ROUTE-RETRY-TIME
If the time expires and the message still has not been sent, the subsystem returns a
nondelivery notification to the sender of the message, except in one case: if the
message was a report, OSI/MHS issues an unroutable report event message instead
of a nondelivery notification.
Start-time, which you can display using the STATUS command, is the time the
message entered the domain, as carried in the TraceInformationElement of the X.400
message: xxx-ROUTE-RETRY-TIME is measured from that time.
Figure 3-5 on page 3-13 illustrates the link and route-retry mechanisms.
ENTRY Object States
An ENTRY object has a summary state of DEFINED only.
Naming ENTRY Objects
A name is given automatically to an ENTRY object when it is created. This name has
the form:
system
is the name of the system (node) that runs the MHS manager process for this
OSI/MHS subsystem.
[\system.]$manager-process.#entry