OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-54
Troubleshooting Example
Step 2: Analyze the Application Using Inspect
Use Inspect to check for error types reported to the application. In this example, the
following information was obtained from the Inspect log:
•
Error received to APS_ASSOC_CONNECTREQ_
•
ERROR 2 received (ZAPS-STATUS-NO-RETRY)
•
EVT 0 received (no significant event occurred)
•
ERR -1001 received (file-system error detected by TAPS)
•
ERRSUB 140 received (type of file-system error: disconnection)
•
SVCID = 5 (you can conclude that the error is returned from TAPS)
Step 3: Review the Statistics Using SCF
Look first at the TAPS status screen to get error information and to get the name of the
TSP process, using either the STATUS or CHECK SU command.
The SCF command
status su $tap1.#z000000 ,detail
displays the following: