Envoy ACP/XF Application Programming Manual

EnvoyACP/XF Application Programming Manual–132179
A-1
A
File-System Errors
This appendix summarizes the EnvoyACP/XF file-system errors. If your local operating
procedures require contacting the Tandem NonStop Support Center (TNSC), supply
your system number and the numbers and versions of all related products as well.
Table A-1
lists the errors in numerical order. These errors fall into three categories:
To expedite recovery when you need to call your Tandem support representative, first
use the SCF TRACE command to collect information about the error, if possible, and
have this information available for the representative.
For general guidelines on error-recovery, see “Error Recovery and Fault-Tolerant
Operation,” after the tables of errors.
Application errors Generally occur because you have not called a file-system
procedure correctly: either you have made an error in coding
or logic, or you have placed the wrong value in a parameter.
Internal system errors May require assistance from your Tandem support
representative.
Hardware errors Sometimes require operator intervention.
Table A-1. Summary of Errors (page 1 of 4)
File-
System
Error
Relevant
Protocol Description Recovery
0 all No error; successful
completion.
Not applicable.
2 all Operation not allowed. Check your program and recode if
necessary; you have requested an
operation that is not supported.
8 all Means one of the following:
•
Frame was received with
P/F bit set to 1.
•
Frame was received with
P/F bit set to 0 and no
more frames are to be
read.
Read MCW.
8 NRM Frame was received with the
P/F bit set to 1, but other
frames may be coming in
from other tributaries. Or, a
frame other than an I-frame
was received.
Read MCW.