| CODE |
MEANING |
| 00 |
Successful I/O operation |
| 10 |
AT END condition |
| 11 |
During a READ NEXT or READ PREVIOUS of an indexed or relative file, another program added a record
to this file. A START statement can be used to reposition the record pointer to the most recently read
record. |
| 21 |
RECORD KEY error. For an indexed or relative file in sequential access mode a WRITE statement
used a RECORD KEY value that was not greater than the value used in the previous WRITE. |
| 22 |
INVALID KEY error:
| (1) |
|
An attempt has been make to write or rewrite a record that would create a duplicate primary key. |
| (2) |
|
An attempt has been made to UN-DELETE a record that has not been deleted. | |
| 23 |
No record exists with the specified RECORD KEY value. |
| 24 |
Index structure is full. Writing a new record would necessitate creating a new index level beyond
the allowable six levels. |
| 30 |
HARDWARE ERROR |
| 34 |
| (1) |
|
No disk space is available to write a new record. |
| (2) |
|
The control point directory size has been exceeded. | |
| 91 |
OPEN error:
| (1) |
|
An open statement referenced a file that was nonexistent, already opened, had an illegal name, for
which the user had an improper ACL, or that did not have an element size that was multiple of four. |
| (2) |
|
An open input statement referenced a file that did not have byte size that was a multiple of 2048. |
| (3) |
|
A CLOSE statement referenced a file that had not been opened. |
| (4) |
|
The filename already existed. |
| (5) |
|
A non-directory argument was in the pathname. |
| (6) |
|
A zero-length filename was specified.
ON a PC this may be caused if the files and buffers are wrong in CONFIG.SYS correct values are (files
= 120) (buffers = 30) | |
| 92 |
Access mode error:
| (1) |
|
File not opened. |
| (2) |
|
WRITE or DELETE attempted to file opened for input. |
| (3) |
|
READ attempted for file opened for output. |
| (4) |
|
OPEN attempted for file closed with lock. |
| (5) |
|
DELETE or REWRITE statement not preceded by a READ statement. Can mean permissions are wrong.
To reset permissions:
cd /mc
chmod -R 777 mcadata
chmod -R 777 mcaobj | |
| 93 |
(1) Cannot delete a permanent file. (2) Directory delete error. |
| 94 |
| (1) |
|
File cannot be accessed because it is in use. |
| (2) |
|
Record cannot be accessed because it is locked. |
| (3) |
|
DELETE FILE attempted for OPEN file. (Usually caused when Backup is being run. Log clearoff. After
complete, try again.) | |
| 96 |
Max number of open files exceeded. |
| 97 |
Maximum number of OPEN files exceeded. |
| 98 |
Attempt to write more than the allowable 65534 records to a relative file. |
| 99 |
Usually means they have more than 48 files on the printer control utility screen. (09.11.15)
Options: Remove, takes the file off list. Delete, takes the file off the hard drive. |
| 9A |
File description inconsistency. Record length, key length, or key positions specified in program
does not agree with data file. |
| 9B |
After a successful OPEN of ISAM file, the runtime system has detected possible corruption in the
file. The file should be closed, which will set the reliability flags and prevent further access to
the file (see 9F). |
| 9C |
Index (.NX) portion of an indexed or relative file is full. |
| 9E |
The record lock limit has been exceeded. |
| 9F |
Possible corruption of an ISAM file has been detected on a attempted OPEN of the file, i.e., the
reliability flags have been set. |
