OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-37
Event-Message Sequences for Common MHS
Functions
2. Event message 36 (ZMHS-EVT-ACCT-RTS-TRANSFER) indicates that the RTS
process received a report from the adjacent MTA.
3. Event message 44 (ZMHS-EVT-ACCT-MRP-ROUTE) indicates that router has
identified the gateway user to whom the report should be delivered and has placed
the report on the queue for the gateway access unit.
4. Event message 7 (ZMHS-EVT-ACCT-MSG) indicates that the report was delivered
and provides summary information about the report.
5. Event message 8 (ZMHS-EVT-ACCT-RECIP-INFO) provides information about the
recipient to whom the report has been delivered.
6. Event message 37 (ZMHS-EVT-ACCT-RTS-ASSOC-END) indicates that the RTS
process has closed the association with the MTA from which the report was
received.
You can use the following common tokens to correlate the events related to this
transaction:
•
Event messages 36, 44, and 7 include the same incoming PDU ID. (ZMHS-TKN-
PDUID in message 36 has the same value as ZMHS-TKN-ORIG-PDUID in event
messages 7 and 44).
•
Event message 44, 7, and 8 include the same report identifier (represented by
tokens of the form ZMHS-TKN-MID-nnnn). Event messages 44 and 7 also
include the same destination O/R name (represented by tokens of the form ZMHS-
TKN-OR-nnnn).
•
Event messages 7 and 8 contain the same subject identifier (represented by
tokens of the form (ZMHS-TKN-SUB-MID-nnnn), which identifies the message as
a result of which the report was produced.
Event Message
Number(s)
Token Name(s)
(ZMHS-TKN-) Token Semantics
36 PDUID Incoming PDUID
44, 7 ORIG-PDUID Incoming PDUID
44, 7, 8 MID-nnnn X.400 MPDU: report identifier
44, 7 OR-nnnn Destination O/R name
7, 8 SUB-MID-nnnn X.400 MPDU: subject identifier