SNAX/APC Management Programming Manual

Appendix A Error Numbers and Error Lists
111813 Tandem Computers Incorporated A–1
This appendix presents all the error numbers provided by the SNAX/APC subsystem
(that is, the values whose symbolic names begin with ZAPC-ERR-) and describes the
error lists associated with these error numbers.
These error numbers can occur as values of the return token, ZSPI-TKN-RETCODE,
and as part of the value of the error token, ZSPI-TKN-ERROR. Standard data
communications error numbers (values whose symbolic names start with ZCOM-ERR-
or ZCMK-ERR-) can also occur in ZSPI-TKN-RETCODE and ZSPI-TKN-ERROR. Refer
to the SPI Common Extensions Manual for information on these error messages.
A description of error lists and how they are retrieved from the buffer is presented in
the SPI Programming Manual. General information about how the SNAX/APC
subsystem handles errors in the token-oriented programmatic interface is given in
Section 1, “Introduction to SNAX/APC.”
Error-handling information pertaining to specific commands and their responses is
given in Section 5, “Commands and Responses.”
In this appendix, all tokens and their values are represented in Data Definition
Language (DDL). For a quick explanation of DDL, see the appendix “Overview of
DDL for SPI” in the SPI Programming Manual.
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 the SNAX/APC Planning and Configuration
Manual).