OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-42
ENTRY Objects
priority, and probable delay of the messages on the queues. The three queues (that is,
the three ENTRY objects) are:
Deferred Message Queue
This queue holds messages whose transmission is deferred to a specific later time at
the request of their originators.
Start-time, which you can display by using the STATUS command, is the time the
message is placed in the deferred message queue.
Link-retry Message Queue
A message in this queue could not be sent on its route because all links to the adjacent
MTA on that route were unavailable. The message waits on the link-retry queue for a
set time (defined by the CLASS attribute LINK-RETRY-DELAY), the subsystem retries
each link in turn, and the message waits again if necessary.
OSI/MHS tries the links in order of priority: the order in which you list the addresses
when you define the MTA object. OSI/MHS does not retry one link before trying the
next one.
After a period of time (specified by the CLASS attribute LINK-RETRY-TIME), if the links
to a particular MTA are still unavailable, the subsystem tries a different route if one is
defined. That is, OSI/ MHS tries to reach the same destination through a different
adjacent MTA, trying each link in priority order if necessary.
As with links, OSI/MHS tries routes in order of priority. You assign priorities to routes
when you define the corresponding ROUTE objects.
Start-time, which you can display by using the STATUS command, is the time
OSI/MHS tried to open an association using the highest-priority link to the adjacent
MTA. LINK-RETRY-TIME is measured from that time.
When the subsystem has tried all links to the message destination in this manner, and
all have failed, the message goes on the route-retry message queue.
Route-retry Message Queue
Each message on this queue waited unsuccessfully on the link-retry queue. No link
could be established to any adjacent MTA on any route selected for the message.
After a set time on the route-retry queue, the subsystem starts over with the first link of
the first route; if the message still cannot be sent, it goes back on the link-retry queue.
The following CLASS attributes determine the initial wait time on the route-retry queue
for each category of message:
URGENT-ROUTE-RETRY-DELAY
NORMAL-ROUTE-RETRY-DELAY
NONURGENT-ROUTE-RETRY-DELAY
REPORT-ROUTE-RETRY-DELAY