OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-35
Event-Message Sequences for Common MHS
Functions
9. Event message 37 (ZMHS-EVT-RTS-ASSOC-END) reports that the RTS process
has closed the association with the MTA to which the message was relayed.
In this example, the message to be relayed came from an adjacent MTA. If it had
come from a gateway or a user agent, event messages 35 and 36 would not have
been produced. (Examples later in this section describe those cases.)
Because these event messages do not always occur in exactly the same sequence—
for example, the associations might be closed in the reverse order—and because they
can be interspersed with other, unrelated events, it is crucial to be able to correlate
related events. You can do so by examining the following common tokens:
•
Event messages 35, 36, and 37 include an association identifier (ZMHS-TKN-
ASSOC-ID), so you can tell which events apply to the same association.
•
Event message 36 includes an incoming or outgoing PDU ID (ZMHS-TKN-PDUID),
depending on the direction of the transfer (ZMHS-TKN-TRANS-DIRECTION), and
event message 7 includes incoming and outgoing PDU IDs (ZMHS-TKN-ORIG-
PDUID and ZMHS-TKN-PDUID, respectively). Therefore you can link the events
that report the arrival and relay of the message with the accounting information that
applies to that transaction. A PDU ID is an OSI/MHS internal identifier that
changes in the life of a message.
•
Event message 44 includes the incoming PDUID (ZMHS-TKN-ORIG-PDUID), so
you can correlate the routing event with the arrival of the message, even if event
message 7 has not yet been produced.