OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-19
Problem Examples
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.... 11 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
-> stats process $zk2.#rk12
MHS stats PROCESS RTS \CS7.$RK12:
Reset-time........ 02 Dec 1994, 12:28:34.446
Sample-time....... 02 Dec 1994, 12:30:56.111
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.... 2 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
-> ==
-> == Inc-assocs-rej has increased since the reset. Stop the trace
-> == and display the MHSRTS records.
-> ==
-> trace process $zk2.#rk12,stop
RTS Process Trace Examination (PTrace)
You use PTrace to examine the content of the trace file. Here is an excerpt, with the
most revealing information shown in boldface:
12/02/94 12:27:75.209702 >000.353366 #9 MHSRTS
Event : RTORQ
Session Connection Id
User reference : 040751515A4B312030
Common Reference : 170D3933303630323139323034355A
Additional Reference : 140135
Calling address
PSEL:
SSEL: 4B5353454C3141
TSEL: 51
NSAP: 51
Called address
PSEL:
SSEL: 4B5353454C3241
TSEL: 52
NSAP: 52
Checkpoint size : 1
Window size : 3
Dialogue mode : 0
Turn : 0
Protocol : 88