2 File-System Errors
Error Codes
The file system of the NonStop operating system returns a code to the calling procedure to indicate
errors and other special conditions. Because most programs use the file system, these conditions
can occur during execution of almost any user-written application or any program supplied by HP.
Many programs display file-system error codes on the user's terminal. These messages typically
contain the code number and a short message. For example:
WARNING - $VOLUME.SUBVOL.FILE ERR 11
To find out what the file-system error means, look up the explanation in this section under the error
code number.
You can obtain a short explanation of any file-system error code or OSS errno value at the TACL
prompt by entering:
ERROR number
If you want to scan a list of all the errors, enter:
ERROR -1
Table 2 lists the major categories of error numbers.
Table 2 File-System Error Categories
CategoryNumber
No error: The operation executed successfully. For C-series procedures, the condition code is set
to "equal to" (CCE).
0
Warning: The operation has executed with the exception of the indicated condition. For warning
6, data is returned in the application process buffer. For C-series procedures, the condition code
is set to "greater than" (CCG).
1-9
Error: The operation encountered an error or a special condition that the application must
recognize, for instance, an aborted transaction on an audited TMF file. For C-series procedures,
the condition code is set to "less than" (CCL).
10-255,
512-32767
Application-defined error: These error numbers are reserved for use by application processes.300-511 (except
538)
FILE^CHECK procedure: This procedure could not return the primary or secondary extent value
because the extent size is greater than 65535 pages.
538
Open System Services error. For information on how to find the meaning of an OSS error, see
“OSS Error Information” (page 279)
4000-4999
NonStop Storage Management Foundation (SMF) error.5000-5999
C-Series and D-Series Error Handling
When an operating-system procedure call returns an error, it is sometimes necessary to call a
second procedure to obtain additional information about the error. Some C-series procedures
return only condition codes and require that a second procedure be called to obtain the file-system
error code; other procedures might require different information to handle the error properly.
When using C-series procedures, additional information about an error on a file is obtained by
calling the FILEINFO procedure. The information returned includes the type of device associated
with the error if you include the devtype parameter in the FILEINFO call and if a device type is
applicable. (For some errors returned by subsystems such as the TMF subsystem, there is no
associated physical device.) Refer to Appendix A in the Guardian Procedure Calls Reference
Manual for a list of the device types and subtypes.
Error Codes 19
To Next Page
Loading...
