OSI/MHS Configuration and Management Manual

Planning Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
3-12
Link Retries and Route Retries
are no more addresses for MTA2, the RTS process reports to the MR process that it
was unable to transfer to MTA2. At that point, the MR process uses a routing table to
determine if there are any alternate routes to MTA2. If there is an alternate route, then
the MR process returns the message to the RTS process for transfer and the link-retry
procedure begins for that route.
If OSI/MHS has tried all the links on all the routes and still failed to deliver the
message, it starts again with the first link on the highest priority route. This procedure
is called “route retry.” You specify how long OSI/MHS should wait before trying again,
and how long it should keep trying, by using the following MR CLASS attributes:
URGENT-ROUTE-RETRY-TIME
URGENT-ROUTE-RETRY-DELAY
URGENT-ROUTE-RETRY-GROW
NORMAL-ROUTE-RETRY-TIME
NORMAL-ROUTE-RETRY-DELAY
NORMAL-ROUTE-RETRY-GROW
NONURGENT-ROUTE-RETRY-TIME
NONURGENT-ROUTE-RETRY-DELAY
NONURGENT-ROUTE-RETRY-GROW
REPORT-ROUTE-RETRY-TIME
REPORT-ROUTE-RETRY-DELAY
REPORT-ROUTE-RETRY-GROW
The description of the ENTRY object in Section 2, Management Environment for
OSI/MHS, explains how these attributes are used. Figure 3-5 illustrates the behavior.