OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-51
Event-Message Sequences for Common MHS
Functions
to the valid recipient both include the O/R name of that recipient in tokens of the
form ZMHS-TKN-OR-nnnn.
•
The instance of event message 7, 8, and 44 pertaining to the report include the
same report identifier in tokens of the form ZMHS-TKN-MID-nnnn.
•
Event message 30, event message 44 pertaining to the valid recipient, and both
instances of event message 7 have the same incoming PDU ID (ZMHS-TKN-
PDUID in message 30, ZMHS-TKN-ORIG-PDUID in message 7).
•
The instance of event message 7 pertaining to the valid recipient has the same
outgoing PDU ID as event message 36 (ZMHS-TKN-PDUID).
•
Event message 44 includes the DSM object name (ZCOM-TKN-OBJNAME) of the
ROUTE object, in the case of the valid recipient, and of the APPL object, in the
case of the gateway user who will receive the report.
Event Message
Number(s)
Token Name(s)
(ZMHS-TKN-) Token Semantics
30, 31 MID-nnnn X.400 MPDU ID
44, 7, 8 (valid
recipient)
MID-nnnn X.400 MPDU ID
7, 8 (report) SUB-MID-nnnn Subject identifier, same as X.400 MPDUID
of original message
30, 7 (valid
recipient)
OR-nnnn Originator’s O/R name
44, 7 (report) OR-nnnn Destination O/R name, same as originator
O/R name for message
31, 8 (report) OR-nnnn Invalid recipient O/R name
44, 8 (valid
recipient)
OR-nnnn Valid recipient O/R name
44 (valid
recipient)
ZCOM-TKN-OBJNAME ROUTE object name
44, 7, 8 (report) MID-nnnn X.400 MPDU: report identifier
44 (report) ZCOM-TKN-OBJNAME Destination APPL object name
30, PDUID Incoming PDUID
7, 44 (valid
recipient)
ORIG-PDUID Incoming PDUID
36, 7 (valid
recipient)
PDUID Outgoing PDUID