OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-36
Event-Message Sequences for Common MHS
Functions
•
Event messages 44, 7, and 8 include a message identifier that you can use to link
the routing event with the summary and recipient information. The message
identifier is the X.400 MPDU ID, represented by tokens with names of the form
ZMHS-TKN-MID-nnnn. Additionally, messages 44 and 8 include the recipient O/R
name (represented by tokens with names of the form ZMHS-TKN-OR-nnnn).
OSI/MHS Delivers a Report to a Gateway
Figure 9-6 illustrates the steps taken when OSI/MHS delivers a report to a gateway.
The numbers on the figure represent the event messages in the order in which they
are produced; the description after the figure gives the actual event numbers.
1. Event message 35 (ZMHS-EVT-ACCT-RTS-ASSOC-OP) indicates that the RTS
process accepted an incoming association.
Event Message
Number(s)
Token Names(s)
(ZMHS-TKN) Token Semantics
35, 36, 37 ASSOC-ID Association identifier
36 PDU-ID Incoming or outgoing PDUID
7 ORIG-PDUID, PDUID Incoming PDUID, outgoing PDUID
44 IORIG-PDUID Incoming PDUID
44, 7, 8 MID-nnn X.400 MPDU ID
44, 8 OR-nnn Recipient O/R name
Figure 9-6. Delivering a Report to a Gateway
045VST .VSD
MRP
3
Gateway
1
MTA
Association
Manager
Router
P1
Decode
Gateway
Access
Unit
Incoming
PDU
Delivered
PDU
RTS
Adjacent
MTA1
4 5
MR PDU
Store
2 6