OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual424827-003
9-8
Symptoms of Interconnection Problems
Symptoms of Interconnection Problems
One of the following symptoms can indicate MTA interconnection problems:
An event message from OSI/MHS reporting RTS association establishment status
or OSI connection problems
An increase in statistics counters on an RTS process object
An OSI/MHS RTS process abends while attempting to communicate with an
OSI/MHS MTA process
Event Message Problem
The event message that reports RTS association establishment status is the following:
ZMHS-EVT-ACCT-RTS-ASSOC-OP - event number 35
REM-T-SELECTOR-n MTA Responder must have value to match LOC-T-
SELECTOR on initiator side.
REM-NSAP-n MTA Responder must have value to match LOC-
NSAP on initiator side. Special
considerations apply to X.25 1980.
CHECKPOINT-SIZE MR class Negotiated down between the two sides.
WINDOW-SIZE MR class Negotiated down between the two sides.
APPLICN-CONTEXT MTA Value must match initiators value.
DIALOGUE-MODE MTA Value must be MONOLOGUE.
MR-TRANSMIT-MODE MR group Must not specify drain mode.
MR-P-SELECTOR MR group Value must match REM-P-SELECTOR on
initiator side.
MR-S-SELECTOR MR group Value must match REM-S-SELECTOR on
initiator side.
MR-T-SELECTOR MR group Value must match REM-T-SELECTOR on
initiator side. Must also match local OSI/AS
ENTRY #TSEL.
MR-NSAP MR group Value must match REM-NSAP on initiator
side and be consistent with local OSI/AS
ENTRY #NSAP and possibly #SNPA and/or
L3PROFILE.
Table 9-2. Attributes Used by the Responder in Association
Establishment (page 2 of 2)
Attribute Name Object Notes