OSI/MHS Configuration and Management Manual
Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-18
Problem Examples
The connection parameters are highlighted in boldface in trace record number 1; they 
include the local and remote OSI addresses, the dialogue mode, the protocol, and the 
initiator’s MTA name and password. Their values must match those expected by the 
adjacent MTA; use SCF if that MTA is an OSI/MHS subsystem, or use whatever other 
means are available if it is not an OSI/MHS subsystem.
In this example, the adjacent MTA (the responder) is an OSI/MHS subsystem, so we 
can proceed as follows to isolate the problem:
1. Check the RTS process statistics for the adjacent MTA by running SCF against the 
remote OSI/MHS subsystem.
2. Run an RTS process trace.
3. Use PTrace to examine the trace file.
RTS Process Statistics
Check the RTS process statistics on the remote system to find out which process is 
rejecting the connection request. Because all three RTS processes of MTA2 share an 
OSI address, a STATS display for any RTS process will demonstrate the problem. The 
display shows that the process has rejected incoming association requests.
-> stats process $zk2.#rk12
MHS stats PROCESS RTS \CS7.$RK12:
Reset-time........ 02 Dec 1994, 12:16:20.127
Sample-time....... 02 Dec 1994, 12:27:16.295
CPU............... 2 Protocol-errors... 0
Msgs-sent......... 0 Msg-bytes-sent.... 0
Msgs-received..... 0 Msg-bytes-received 0
Inc-assocs-open... 0 Out-assocs-open... 0
Inc-assocs-closed. 0 Out-assocs-closed. 0
Inc-assocs-rej.... 9 Out-assocs-rej.... 0
Inc-assocs-fail... 0 Out-assocs-fail... 0
Inc-assocs-recovs. 0 Out-assocs-recovs. 0
Inc-trans-fail.... 0 Out-trans-fail.... 0
Transfer-timeouts. 0 Recovery-timeouts. 0
U-ABORT........... 0 P-ABORT........... 0
U-EXCEPT.......... 0 P-EXCEPT.......... 0
RTS Process Trace
Below is a trace of the same RTS process. A trace allows examination of the 
responder’s RTS actions. 
-> trace process $zk2.#rk12,select mhsrts, to trrts, recsize 4000
-> ==
-> == wait for something to happen
-> ==
-> stats process $zk2.#rk12, reset
MHS stats PROCESS RTS \CS7.$RK12:
Reset-time........ 02 Dec 1994, 12:16:20.127
Sample-time....... 02 Dec 1994, 12:28:23.901
CPU............... 2 Protocol-errors... 0










