


Following is a brief description of the secondary error codes for error 98s for the Vision file system.
| 01
| The file size listed in the file's header does not match the actual file size.
|
| 02
| The header's next record pointer points to an area that is invalid.
|
| 03
| Unique ID used to distinguish duplicate keys has already been used and cannot
be used with a new key.
|
| 04
| Missing tree terminator key.
|
| 05
| An error was detected while performing a bulk read of a record.
|
| 06
| The key being deleted from the tree was not found in the tree.
|
| 07
| A child node was not found in its parent.
|
| 08
| An I/O error occurred when the runtime was trying to read key information out
of the file's header.
|
| 09
| A pointer in a node points past the end of the file.
|
| 12
| A node in the free node list was not marked as a free node.
|
| 13
| A record in the deleted record list was not marked as a deleted record.
|
| 20
| Non-zero key prefix on first key in node.
|
| 21
| Key prefix larger than key size.
|
| 22
| Key prefix or key size larger than maximum key size.
|
| 31
| A record pointer in a Vision Version 3 file points to a record-chain value.
In a Version 3 file, record pointers should always point to the start of a
record, never to a record-chain value.
|
| 68
| A Vision 4 data segment is not found during an open.
|
| 69
| A Vision 4 index segment is not found during an open.
|
| 81
| Invalid data found in record header when a compressed record was read.
|
| 82
| Invalid data found in record header when a non-compressed record was read.
|
| 83
| When a record was read, an I/O error occurred or the record was too short.
|
| 84
| When a record link was read, an I/O error occurred or the link was too small.
|
| 85
| Record contains invalid record compression codes--the record would uncompress
into a record that was larger than the maximum record size.
|
| 86
| During a record write, a read of a record-chain value failed, probably due to
an end-of-file condition.
|
| 87
| Vision Version 4 detects that it is about to write a record to an area of a
file that does not contain an appropriate record header. An appropriate record
header indicates that a record currently does not exist at this address.
|
| 89
| In Vision Version 4, on open, a data segment's internal revision number does
not match the internal revision number stored in the header of the first data
segment.
|
| 90
| In Vision Version 4, on open, an index segment's internal revision number does
not match the internal revision number stored in the header of the first data
segment.
|
| 99
| Vision Version 4 has tried to open the 65,537th data or index segment for this file. Vision can only support 65,536 data segments and 65,536 index segments per logical file. |