OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-24
Troubleshooting Example
The SCF command
stats service $tap1.#l5
displays the following:
This screen shows that only one SPDU was received by the TAPS process—the connect
request. The display also shows that a refuse SPDU was sent in response. The reason
code in the refuse SPDU tells the sender that a retry for the connect is not possible using
the original connect primitive attributes.
The next step is to ensure that the subdevice that was returned by the call to
APS_STATUS_ is active and in a STARTED state. The subdevice is called
$TAP1.#Z00000P, as displayed by the Inspect command you issued after the
APS_STATUS_ call.
You can verify the subdevice name, if you want. The SCF command
names su $tap1.*
displays the following:
OSIAS Stats SERVICE \MARS.$TAP1.#L5
Reset Time.... 15 Oct 1991, 13:39:46.637
Sample Time... 15 Oct 1991, 13:40:13.157
Refuse SPDUs: Received Threshold Sent Threshold
No reason.............. 0 -- 0 --
Permanent.............. 0 0 1 0
Temporary.............. 0 0 0 --
Other.................. 0 -- 0 --
Abort SPDUs:
No reason.............. 0 -- 0 --
Protocol Error......... 0 -- 0 0
Other.................. 0 -- 2 --
Connect SPDUs............ 1 0
Accept SPDUs............. 0 0
Disconnect SPDUs......... 0 0
Not Finished SPDUs....... 0 0
Finish SPDUs............. 0 0
Total Refuse/Abort SPDUs.... 0 1
Total SPDUs................. 1 1
Total SPDU Bytes............ 547 8
Total Data Bytes............ 0 0
Subdevice Summary:
Attach pending SUs...... 4
Active connection SUs... 0
Inactive (static) SUs... 20
Available SUs........... 100
OSIAS Names SU \MARS.$TAP1.*
SU
$TAP1.#Z00000P $TAP1.#Z00000Q $TAP1.#Z00000R $TAP1.#Z00000S