Guardian Procedure Errors and Messages Manual

Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Your system operator might be able to recover the file.
55 (%67) I/O error in disk directory; the file
is no longer accessible. (device type: 3)
Cause A severe problem occurred on a disk volume used by the file system. The file associated
with the error is no longer accessible.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Your system operator might be able to recover the file.
56 (%70) I/O error on disk volume label;
the volume is no longer accessible.
(device type: 3)
Cause A severe problem occurred on a disk volume used by the file system. The volume associated
with the error is no longer accessible.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Your system operator might be able to recover the file.
57 (%71) The disk free space table is full.
(device type: 3)
Cause A severe problem occurred on a disk volume used by the file system. There might not be
enough contiguous free disk space to enlarge the disk free space table.
Effect The procedure sets the error code and returns without performing the requested operation.
The file associated with the error is no longer accessible.
Recovery Your system operator might be able to recover the file.
58 (%72) The disk free space table is marked bad.
(device type: 3)
Cause A severe problem occurred with the accessed disk volume. The file associated with the error
is no longer accessible.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Your system operator might be able to recover the file.
59 (%73) The disk file is bad; there is a mismatch
in the internal FCB, or the file structure
in a structured file is inconsistent.
(device type: 3)
This error can occur during an attempt to open a file, or during an attempt to read or write to a
structured file. It might indicate that the file or table is broken.
If an application uses unstructured access to write to a DP2 structured file, it is possible that future
attempts to read or write to this file using unstructured access will cause this error. User applications
must not use unstructured access to write to a structured file.
Another example of this error occurring follows a RESTORE operation on a key-sequenced file that
was backed up while it was being modified. The error eventually occurs because the file is
inconsistent.
34 File-System Errors