Table of Contents
Advertisement
21 File-System Errors
Some file-system errors are new or changed for the Neoview platform and are not documented,
see
"New or Changed File-System Errors for the Neoview Platform" (page
Some error messages generated by the Neoview platform include file-system error codes. For
example:
SQL 1024
1024 File system error error-number occurred on text-string-1.
text-string-2.
This section lists all file-system error codes and provides the corresponding error text for each
code number. The error text can sometimes help you troubleshoot a problem. If the initial error
message and file-system error text are insufficient to help you solve a problem, or if you need
more information, contact the GMCSC.
Error Number
0000
0001
0002
0003
0004
0005
0006
0007
0008
0009
0010
0011
0012
0013
0014
0015
0016
0017
0018
0019
0020
0021
0022
File-System Error Text
The operation completed successfully.
A read procedure reached end-of-file or a write procedure reached end of tape.
The operation specified is not allowed on this type of file.
An open or purge of a partition failed.
An open operation for an alternate key file failed.
Sequential buffering not used because no space was available in the process-control buffer for the
sequential block buffer.
A system message was received from another process.
This process cannot accept a command because the receiving file is not opened correctly.
The operation was successful (examine message control word for additional status).
A read through a locked record was successful.
The new record or file could not be created because a file by that name or a record with that key
already exists.
The file is not in the directory or the record is not in the file, or the specified tape file is not on a
labeled tape.
The file is in use.
The filename was not specified in proper form.
That device does not exist on this segment.
The disk or segment specified for a file RENAME operation does not match the name of the disk
or segment of the file.
No file with that file number has been opened.
A paired-open was specified and the file is not open by the primary process, the parameters
supplied do not match the parameters supplied when the file was opened by the primary, or the
primary process is not alive.
The segment specified does not exist in the network.
There is no more space for devices in the logical device table.
File name is too long to be opened across a network, or swap file or segment name is not acceptable.
An illegal count was specified in a file-system call, or the operation attempted to transfer too
much or too little data.
The application parameter or buffer address is out of bounds.
398).
385
Advertisement
Table of Contents
