OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-26
Problem Description
Each message processed by the MTA is typically destined for more than one recipient.
The MTA is responsible for splitting such messages, with multiple recipients requiring
different routing. The MTA is also responsible for adding to each message both
internal and external trace information, which records the path the message has taken
through the MHS.
The log records are designed to keep track of the processing performed for each
recipient, and only when all of its recipients have been processed completely can an
original incoming message be discarded.
Most of the log records fall into the following three categories:
•
Records that log the start of a processing sequence for multiple recipients. These
records include RX_confirmed, DECODED, and SUBMITTED logs.
•
Records that log the end of a processing sequence for multiple recipients. These
records include DELETED, CANCELLED, DELIVERED, NOTIFIED, and
TX_REQUESTED log records.
•
Records that log the creation of a new PDU for multiple recipients. These records
include CREATED and ENCODED log records.
The other log types that are relevant to the MTA are the TX_FAILED,
LD_UNROUTABLE, and LD_UNDECODEABLE log records. A log type specific to
gateways is LD_ARCHIVED; records of this type describe PDUs that the GPI was
unable to decode or that the GPI application archived for any reason.
The OSI/MHS store cleaner (SC) process periodically scans through the PDU store,
searching for PDUs that have been fully processed and can therefore be deleted. The
log records associated with a PDU are used to determine whether the PDU has been
fully processed. If so, it and its associated log records are deleted by the SC process.
If the log records indicate that a PDU was undecodable or unroutable or that it was
archived by a gateway, the PDU is not deleted.
The use of background processing to delete fully processed PDUs is a more efficient
solution than having the MR process check for completeness whenever a significant
event happens to a PDU. However, this approach implies the use of a large PDU store
for an MR group to allow for periods when the MTA is busy but the store cleaner is
being run infrequently.
The OSI/MHS log records are not externally accessible (except through a specialized
diagnostic tool available to HP technical support). To help you track the progress of a
message through the system, OSI/MHS processes also produce event messages.
These messages are available for display through various interfaces (such as
Viewpoint or an EMS printing distributor); they are also available for processing by your
management applications. Because these messages are especially useful for
message tracking, they are described in more detail in Message Tracking on
page 9-31.