OSI/MHS Configuration and Management Manual
Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-15
Problem Examples
U-ABORT........... 0 P-ABORT........... 0
U-EXCEPT.......... 0 P-EXCEPT.......... 0
-> ==
-> == Check the RTS processes stats
-> ==
-> stats process $zk1.#rk11
MHS stats PROCESS RTS \CS7.$RK11:
Reset-time........ 02 Dec 1994, 12:26:10.355
Sample-time....... 02 Dec 1994, 12:28:35.784
CPU............... 0 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.... 0 Out-assocs-rej.... 2
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
The Out-assoc-rej count has increased since the reset, indicating that more attempts
have been rejected. Stop the trace and use PTrace to examine it:
-> ==
-> == Now stop traces
-> ==
-> trace process
$zk1.#rk11,stop
To examine the contents of the RTS process trace, use the PTrace object and select
only the MHSRTS events. The following trace records have been taken from a log file
produced by PTrace. The log file is normally a 132-column display, so some lines wrap
in the following displays. Ellipses (...) indicate that some trace records have been
omitted from the example. The events of interest begin when the open request occurs,
represented by the event record containing RT_OPreq. Give special attention to the
elements highlighted in boldface.
12/02/94 12:24:45.039624 >000.000000 #1 MHSRTS
Event : RT-OPreq
Local address
PSEL:
SSEL: 4B5353454C3141
TSEL: 51
NSAP: 51
Remote address
PSEL:
SSEL: 4B5353454C3241
TSEL: 52
NSAP: 52
dialogue mode : 0
turn : 0
protocol : 88
abstract syntax id : 0
MTA Name : 4D544131
Password : 4D544132
--------------------------------------------
Context 1129240
Status : 1 Valid user link : 1 Valid session link : 0 Direction : 2
State : 0 Queueing enabled : 0