Eloquence DBMS status
|
0 |
Successful execution - no error. |
-1 |
No such database.
Database is currently opened in an incompatible mode.
Bad root file reference.
Database opened exclusively.
|
-2 |
Database in use (Eloquence library only)
|
-3 |
User name not recognized
|
-4 |
User password does not match
|
-10 |
User may not open additional databases, maxiumum (20) are already opened.
|
-11 |
Bad database name or preceding blanks missing
|
-12 |
DBPUT, DBDELETE, or DBUPDATE called with database not locked.
|
-14 |
DBPUT, DBDELETE, and DBUPDATE not allowed in access mode 8
|
-21 |
Bad password - grants access to nothing.
Data item nonexistent or inaccessible.
Data set nonexistent or inaccessible.
Data set volume nonexistent.
|
-23 |
User lacks write access to data set.
|
-24 |
DBPUT, DBDELETE, or DBUPDATE not allowed on automatic master
|
-31 |
Bad mode.
DBGET mode 5 - Specified data set lacks chains.
DBGET mode 7 - Illegal for detail data set.
|
-35 |
A deadlock condition has been detected.
|
-52 |
Item specified is not an accessible search item in the specified set.
Bad LIST variable - must be "@ ", "@;" or "@".
|
-91 |
Root file not compatible with Eloquence revision
|
-92 |
Database requires creation
|
-94 |
Data or structure information lost. Database must be erased or re-created.
|
-95 |
No automatic master set entry for current detail. DBDELETE only.
|
-96 |
Corrupt pointer value detected in current data set.
see also
|
-120 |
Not enough memory to perform DBLOCK
|
-122 |
Descriptor list bad. Not within string limits.
|
-123 |
Illegal relational operator.
|
-124 |
Descriptor too short; must be greater than or equal to 9 words
|
-125 |
Bad set name or number.
|
-126 |
Bad item name or number.
|
-127 |
Attempt to lock using a compound item.
|
-128 |
Bad descriptor length for numeric item.
|
-124 |
Two descriptors conflict
|
-135 |
Second lock is not allowed in modes 1, 3, 5, 11, 13, and 15.
|
-136 |
Descriptor list exceeds 4092 bytes.
|
-137 |
Qualifier parameter is of wrong type
|
-700 |
Communication with the database server failed
Last element of status array contains error details.
see also
|
-800 |
ISAM error (Eloquence A.05.xx).
Last element of status array contains ISAM error number.
see also
|
-801 |
Volume failure.
Last element of status array contains error details.
see also
|
-802 |
Node related failure.
Last element of status array contains error details.
see also
|
-803 |
FixRec related problem
Last element of status array contains error details.
see also
|
-804 |
BTREE related problem
Last element of status array contains error details.
|
-805 |
SysCat related problem
Last element of status array contains error details.
|
-806 |
System call failed.
Last element of status array contains error details.
|
-807 |
DBLOCK failure detected.
A failure condition was detected by DBLOCK.
Last element of status array contains error details.
If the tenth status element is -3, a thread blocked on a DBLOCK
was cancelled with dbctl.
|
-808 |
Management API internal failure.
A failure condition was detected by the management API.
This should never happen.
Last element of status array contains error details.
|
-809 |
A failure condition was detected by the IMAGE subsystem.
This should never happen.
Last element of status array contains error details.
|
-900 |
Internal eloqdb5 server failure condition (Eloquence A.05.xx).
|