OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-50
Event-Message Sequences for Common MHS
Functions
1. Event message 30 (ZMHS-EVT-ACCT-CUG-VIOL) indicates that the router
discovered a CUG violation. That is, it discovered that a recipient of an incoming
message is not a member of the same closed user group as the originator and has
queued the message for the notification handler.
2. Event message 31 (ZMHS-EVT-ACCT-CUG-VIOL-RECIP) provides information
about the invalid recipient.
3. Event message 44 (ZMHS-EVT-ACCT-MRP-ROUTE) indicates that router has
identified the valid recipient and has queued the message for the association
manager.
4. Event message 44 (ZMHS-EVT-ACCT-MRP-ROUTE) indicates that the router has
identified the route to use for delivering the report (of the CUG violation), and has
queued the report for the gateway access unit because the originator of the
message was a gateway user.
5. Event message 7 (ZMHS-EVT-ACCT-MSG) indicates that the message was sent
to the valid recipient and provides summary information about the message.
6. Event message 8 (ZMHS-EVT-ACCT-RECIP-INFO) provides information about the
valid recipient of the message.
7. Event message 36 (ZMHS-EVT-ACCT-RTS-TRANSFER) indicates that the RTS
process relayed the message to the adjacent MTA.
8. Event message 7 (ZMHS-EVT-ACCT-MSG) indicates that the report of the CUG
violation was queued for the gateway access unit (for delivery to the gateway user
who originated the message), and it provides summary information about the
message.
9. Event message 8 (ZMHS-EVT-ACCT-RECIP-INFO) provides information about the
recipient of the message who was in violation of CUG rules.
You can use the following common tokens to correlate the events related to this
transaction:
•
Event messages 30 and 31, and the instances of event message 7, 8, and 44 that
pertain to the valid recipient include the same message identifier, in tokens of the
form ZMHS-TKN-MID-nnnn. That message identifier is the same as the subject
identifier (represented by tokens with names of the form ZMHS-TKN-SUB-MID-
nnnn) in the instances of event messages 7 and 8 that pertain to the report.
•
Event message 30 and the instance of event message 7 pertaining to the valid
recipient include the originator O/R name, which is the same as the destination
O/R name in instances of event message 7 and 44 pertaining to the report. That
is, the tokens with names of the form ZMHS-TKN-OR-nnnn have the same values
in all those cases.
•
Event message 31 and the instance of event message 8 pertaining to the report
have the same recipient name (the name of the invalid recipient), in tokens of the
form ZMHS-TKN-OR-nnnn). The instances of event message 44 and 8 pertaining