SNAX/APC Configuration and Management Manual

SCF Error Messages for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
C-2
Before You Report a Problem
Before You Report a Problem
Some error messages are not easily recoverable and require you to seek additional help.
In these cases, follow the standard procedures at your site for contacting the appropriate
support personnel. These procedures might involve contacting the Tandem NonStop
Support Center or your local Tandem support representative.
Collect any relevant information before reporting the problem. The minimal
information required for reporting a problem against T9096 SNAX/APC includes:
1. System number and version procedure from the APCOBJ module; the version
procedure can be obtained by entering VPROC or BIND:
VPROC
Enter filename:
>$system-volume.subvolume.APCOBJ
2. Versions of all related products.
3. Problem description and symptoms—include a description of the problem and the
accompanying symptoms.
4. SNAX/APC trace file showing the problem—the trace file is assigned either at
SNAX/APC startup or when a dynamic trace is invoked. It is recommended that the
trace be taken specifying SELECT ALL so that support and problem resolution
personnel can see the entire picture. A trace of the problem is mandatory for
problem resolution.
If the problem seems to be in establishing sessions, specify tracing using the
SNAX/APC startup parameters (see Part I, SNAX/APC Planning and
Configuration).
5. EMS logs—include the event (EMS) logs that were active when the problem
occurred.
6. Saveabend file—if SNAX/APC abends or hangs, it is important to get the SAVE file
of the SNAX/APC server. To accomplish this, when SNAX/APC drops into Inspect,
or if it hangs and you invoke Inspect using the DEBUG command, issue the SAVE
command.
7. Configuration/Startup files—if a configuration problem is suspected, the SCF
configuration file or an SCF command display of the following command can be
useful:
INFO PROCESS $apc-process-name, SUB ALL, DETAIL
8. Other files—other files might include APCLMAP, which resides on the SNAX/APC
installation subvolume and is used in formatting traces, and SNAX line trace files
from the underlying access method (SNAX/XF, SNAX/APN, or SNAX/CDF).
SNAX line trace files might be helpful when all else fails or when a low-level
problem (that is, within the lower SNA layers or basic line connectivity) is
encountered. The SNAX line trace should be accompanied by the SCF displays of
the SNAX lines, physical units (PUs) and logical units (LUs) that SNAX/APC
utilizes.