HP 3000 Manuals HP 3000 Manuals
Using TurboIMAGE/XL Intrinsics (Cont.)
DBERROR
INTRINSIC NUMBER 419.
Moves a message, as an ASCII character string, to a buffer specified by
the calling program. The message interprets the contents of the status
array as set by a call to a TurboIMAGE/XL procedure.
Syntax.
DBERROR,status,buffer,length
Parameters.
status is the name of the array used as the status
parameter in the TurboIMAGE/XL procedure call about
which information is requested.
buffer is the name of an array in the calling program's
data area, at least 36 halfwords long, in which the
message is returned.
length is a short, 16-bit integer variable which is set by
DBERROR to the positive byte length of the message
placed in the buffer array. The length will never
exceed 72 characters.
NOTE The call to DBERROR must be made immediately after receiving an
error status before any other intrinsics are executed to ensure the
display of valid messages.
Discussion.
Like DBEXPLAIN, DBERROR messages are appropriate and helpful when
debugging application programs. The errors they describe are, for the
most part, errors that do not occur in a debugged and running program.
Some errors or exceptional conditions are expected to occur, even in a
production environment. For example, the MPE/iX intrinsic DBOPEN can
fail due to concurrent database access. In this case, printing the
following DBERROR message:
DATABASE OPEN EXCLUSIVELY
can be perfectly acceptable, even to the person using the application
program. However, in many cases a specific message produced by the
application program is preferable to the one produced by DBERROR. A
DBFIND error generated by the application program, such as:
THERE ARE NO ORDERS FOR THAT PART NUMBER
would be more meaningful to a user entering data at a terminal than the
DBERROR message:
THERE IS NO CHAIN FOR THE SPECIFIED SEARCH ITEM VALUE
Table 5-10 lists all messages that can be returned by DBERROR with
their corresponding return status values. Variable information is
represented by a lowercase word or phrase. Several messages can
correspond to one return status and the interpretation of the value
depends on the context in which it is returned; the message returned
depends on additional information returned by the TurboIMAGE/XL
intrinsic.
Table 5-10. DBERROR Messages
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| 0 | SUCCESSFUL EXECUTION - NO ERROR |
| | |
| -1 | NO SUCH DATABASE |
| | DATABASE OPEN IN AN INCOMPATIBLE MODE |
| | BAD ACCOUNT REFERENCE or BAD GROUP REFERENCE |
| | BAD ROOT FILE REFERENCE |
| | INSUFFICIENT DISC SPACE |
| | VIRTUAL MEMORY NOT SUFFICIENT TO OPEN ROOT FILE |
| | DATABASE ALREADY OPEN FOR MORE THAN READ |
| | DATABASE IN USE |
| | DATABASE OPEN EXCLUSIVELY |
| | MPE SECURITY VIOLATION |
| | MPE FILE ERROR decimal integer RETURNED BY FOPEN |
| | |
| | |
| | ON { ROOT FILE } |
| | { DATA SET # decimal integer} |
| -2 | EXCEEDS GROUP DISC SPACE |
| | EXCEEDS ACCOUNT GROUP DISC SPACE |
| | DUPLICATE FILE NAME |
| | MPE FILE ERROR decimal integer RETURNED BY FCLOSE |
| | |
| | |
| | ON { ROOT FILE } |
| | { DATA SET # decimal integer} |
| -3 | MPE FILE ERROR decimal integer RETURNED BY FREADDIR |
| | |
| | |
| | ON { ROOT FILE } |
| | { DATA SET # decimal integer} |
| -4 | MPE FILE ERROR decimal integer RETURNED BY FREADLABEL |
| | |
| | |
| | ON { ROOT FILE } |
| | { DATA SET # decimal integer} |
| -5 | MPE FILE ERROR decimal integer RETURNED BY FWRITEDIR |
| | |
| -6 | MPE FILE ERROR decimal integer RETURNED BY FWRITELABEL |
| | |
| -7 | PREVIOUS MPE FILE ERROR decimal integer FOUND IN DESIRED BUFFER |
| | |
| -8 | MPE FILE ERROR decimal integer RETURNED BY FUNLOCK |
| | |
| -9 | CANNOT CREATE control block name: MPE ERROR nn |
| | |
| -10 | MPE FILE ERROR decimal integer RETURNED BY FFILEINFO |
| | |
| -11 | BAD DATABASE NAME OR PRECEDING BLANKS MISSING |
| | BAD DATABASE REFERENCE (FIRST 2 CHARACTERS) |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| -12 | DATABASE MUST BE IN LOGON GROUP AND ACCOUNT |
| | intrinsic name CALLED WITHOUT COVERING LOCK IN EFFECT |
| | |
| -13 | NOT ALLOWED; MUST BE CREATOR OF ROOT FILE OR DATABASE |
| | |
| -14 | CALLS TO intrinsic name NOT ALLOWED IN ACCESS MODE decimal |
| | integer |
| | |
| -15 | DSLINE OR REMOTE HELLO FAILURE: SETUP FOR RDBA FAILED |
| | |
| -21 | BAD PASSWORD - GRANTS ACCESS TO NOTHING |
| | DATA ITEM NONEXISTENT OR INACCESSIBLE |
| | SPECIFIED INTRINSIC CANNOT ACCESS THE DATA SET |
| | DATA SET NONEXISTENT OR INACCESSIBLE |
| | BAD MAINTENANCE WORD (CONTAINS COMMA OR DOES NOT MATCH) |
| | ILLEGAL NUMBER OF BUFFERS REQUESTED |
| | |
| -22 | MAINTENANCE WORD REQUIRED |
| | |
| -23 | USER (CLASS) LACKS WRITE ACCESS TO DATA SET |
| | |
| -24 | OPERATION NOT ALLOWED ON AUTOMATIC MASTER DATA SET |
| | |
| -30 | MPE V ILR ENABLED; ONLY DBOPEN (MODE 1-8) AND DBUTIL |
| | DISABLE ILR ALLOWED |
| | |
| -31 | DBGET MODE decimal integer ILLEGAL FOR DETAIL DATA SET |
| | DBGET MODE decimal integer BAD--SPECIFIED DATA SET LACKS CHAINS |
| | BAD (UNRECOGNIZED) intrinsic name MODE: decimal integer |
| | |
| -32 | UNOBTAINABLE ACCESS MODE: AOPTIONS REQUESTED:%octal integer, |
| | GRANTED:%octal integer |
| | |
| -33 | MODE 7 DIAGNOSTICS NOT ALLOWED |
| | |
| -34 | DATABASE MUST BE RECOVERED BEFORE ACCESS IS ALLOWED. |
| | |
| -51 | LIST TOO LONG OR NOT PROPERLY TERMINATED |
| | |
| -52 | ITEM SPECIFIED IS NOT AN ACCESSIBLE SEARCH ITEM IN THE |
| | SPECIFIED SET |
| | BAD LIST - CONTAINS ILLEGAL OR DUPLICATED DATA ITEM |
| | REFERENCE |
| | |
| -53 | DBPUT LIST IS MISSING A SEARCH OR SORT ITEM |
| | |
| -60 | ILLEGAL FILE EQUATION FOR ROOT FILE[REV BEG] |
| | |
| -61 | ERROR WHILE OBTAINING INFORMATION ABOUT FILE EQUATION.[REV END] |
| | |
| -80 | OUTPUT DEFERRED NOT ALLOWED WITH ILR ENABLED |
| | |
| -81 | OUTPUT DEFERRED NOT ALLOWED WITH ROLLBACK ENABLED |
| | |
| -82 | CIUPDATE IS SET TO DISALLOWED; CANNOT USE CRITICAL ITEM UPDATE |
| | [REV BEG] |
| | |
| -88 | DATABASE BAD: THIRD PARTY INDEXING WAS IN PROCESS (INDEX AGAIN) |
| | |
| -89 | DATABASE BAD RESTRUCTURING WAS IN PROCESS (RESTORE DATABASE)[REV |
| | END] |
| | |
| -90 | ROOT FILE BAD: UNRECOGNIZED STATE: %octal integer |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| -91 | ROOT FILE (DATABASE) NOT COMPATIBLE WITH CURRENT TURBOIMAGE |
| | INTRINSICS |
| | |
| -92 | DATABASE REQUIRES CREATION (VIRGIN ROOT FILE) |
| | |
| -93 | DATABASE ALREADY EXISTS. |
| | |
| -94 | DATABASE BAD: OUTPUT DEFERRED, MAY NOT BE ACCESSED IN MODE |
| | decimal integer |
| | |
| -95 | DATABASE BAD - CREATION WAS IN PROCESS (CREATE AGAIN) |
| | |
| -96 | DATABASE BAD - ERASE WAS IN PROCESS (ERASE AGAIN) |
| | |
| -97 | DATABASE BAD - ILR ENABLE IN PROGRESS (ENABLE AGAIN) |
| | |
| -98 | DATABASE BAD - ILR DISABLE IN PROGRESS (DISABLE AGAIN) |
| | |
| -99 | UNSUPPORTED FEATURE. |
| | |
| -100 | MPE ERROR decimal integer RETURNED BY DSOPEN |
| | |
| -101 | MPE ERROR decimal integer RETURNED BY DSCLOSE |
| | |
| -102 | MPE ERROR decimal integer RETURNED BY DSWRITE |
| | |
| -103 | REMOTE 3000 STACK SPACE INSUFFICIENT |
| | |
| -104 | REMOTE 3000 DOES NOT HAVE TURBOIMAGE/XL. |
| | |
| -105 | REMOTE 3000 CANNOT CREATE TURBOIMAGE CONTROL BLOCK |
| | |
| -106 | REMOTE 3000 DATA INCONSISTENT |
| | |
| -107 | NS/3000 OR DS/3000 SYSTEM ERROR |
| | |
| -108 | HPUNLOADCMPROCEDURE CALL FAILED |
| | |
| | (The bracketed numbers in the following messages -110 to - 112 |
| | refer to the value in halfword 2 of the status array. For other |
| | error numbers, refer to WRITELOG in the MPE/iX Intrinsics |
| | Manual.) |
| | |
| -109 | ERROR RETURNED BY LOGINFO INTRINSIC. |
| | |
| -110 | OPENLOG RETURNED ERROR NUMBER nn TO DBOPEN |
| | LOGGING ENABLED AND NO LOG PROCESS RUNNING [3] |
| | DATABASE CONTAINS INVALID LOGID PASSWORD [8] |
| | LOG FILE CAN'T OBTAIN NECESSARY DISC SPACE [12] |
| | MAXIMUM USER COUNT PER LOG PROCESS REACHED [13] |
| | END OF FILE ON LOGFILE [15] |
| | DATABASE CONTAINS INVALID LOG IDENTIFIER [16] |
| | |
| -111 | WRITELOG RETURNED ERROR NUMBER nn TO intrinsic name |
| | LOG PROCESS TERMINATED [3] |
| | LOG FILE CAN'T OBTAIN NECESSARY DISC SPACE [12] |
| | END OF FILE ON LOGFILE [15] |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| -112 | CLOSELOG RETURNED ERROR NUMBER nn TO intrinsic name |
| | LOG PROCESS TERMINATED [3] |
| | LOG FILE CAN'T OBTAIN NECESSARY DISC SPACE [12] |
| | END OF FILE ON LOGFILE [15] |
| | |
| -113 | FLUSHLOG RETURNED ERROR NUMBER nn TO DBEND |
| | |
| -114 | ROLLBACK ENABLED WITHOUT ENABLING LOGGING |
| | |
| -120 | OUT OF STACK SPACE TO PROCV. |
| | |
| -121 | ILLEGAL LOCK DESCRIPTOR COUNT |
| | |
| -123 | ILLEGAL RELATIONAL OPERATOR |
| | |
| -124 | DESCRIPTOR LENGTH ERROR; MUST BE 9 OR MORE |
| | |
| -125 | ILLEGAL SET NAME OR NUMBER IN DESCRIPTOR |
| | |
| -126 | ILLEGAL ITEM NAME OR NUMBER IN DESCRIPTOR |
| | |
| -127 | ILLEGAL ATTEMPT TO LOCK ON A COMPOUND ITEM |
| | |
| -128 | VALUE FIELD TOO SHORT FOR THE ITEM SPECIFIED |
| | |
| -129 | P28 IS LONGEST P-TYPE ITEM THAT CAN BE LOCKED |
| | |
| -130 | ILLEGAL DECIMAL DIGIT IN TYPE 'P' DATA VALUE |
| | |
| -131 | LOWERCASE CHARACTER IN TYPE 'U' DATA VALUE |
| | |
| -132 | ILLEGAL DIGIT IN TYPE 'Z' DATA VALUE |
| | |
| -133 | ILLEGAL SIGN CHARACTER IN TYPE 'Z' DATA VALUE |
| | |
| -134 | TWO LOCK DESCRIPTORS CONFLICT IN SAME REQUEST |
| | |
| -135 | DBLOCK CALLED WITH LOCKS ALREADY IN EFFECT IN THIS JOB/SESSION |
| | |
| -136 | DESCRIPTOR LIST LENGTH EXCEEDS 4094 BYTES |
| | |
| -137 | USER ABOUT TO WAIT FOR SELF. |
| | |
| -139 | INVALID NUMBER OF BASE IDs. |
| | |
| -140 | BAD BASE ID LIST. |
| | |
| -141 | ALL MDBX DATABASES MUST BE ON THE SAME SYSTEM. |
| | |
| -142 | ALL MDBX DATABASES LOG TO THE SAME LOG FILE. |
| | |
| -143 | LOGGING MUST BE ENABLED OR DISABLED FOR ALL MDBX DATABASES. |
| | |
| -144 | MUSTRECOVER MUST BE ENABLED OR DISABLED FOR ALL MDBX DATABASES. |
| | |
| -145 | ROLL-BACK MUST BE ENABLED OR DISABLED FOR ALL MDBX DATABASES. |
| | |
| -146 | INVALID TRANSACTION ID. |
| | |
| -147 | MODE DOESN'T MATCH DBBEGIN MODE. |
| | |
| -148 | BASE ID LIST DOESN'T MATCH DBBEGIN BASE ID LIST. |
| | |
| -151 | TEXT LENGTH GREATER THAN 512 BYTES |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| -152 | DBCLOSE CALLED WHILE A TRANSACTION IS IN PROGRESS |
| | DBBEGIN CALLED WHILE A TRANSACTION IS IN PROGRESS |
| | DBXBEGIN CALLED WHILE A TRANSACTION IS IN PROGRESS |
| | |
| -153 | DBEND CALLED WHILE NO TRANSACTION IS IN PROGRESS |
| | |
| -160 | FILE CONFLICT: A FILE ALREADY EXISTS WITH THE ILR LOG FILE NAME |
| | |
| -161 | CANNOT CHECK FOR AN ILR LOG FILE CONFLICT: FILE SYSTEM ERROR nn |
| | |
| -166 | CANNOT PURGE ILR LOG FILE: FILE SYSTEM ERROR nn |
| | |
| -167 | CANNOT BEGIN MPE XL XM TRANSACTION: XM ERROR nn |
| | |
| -168 | CANNOT ATTACH DATA SET # decimal integer to MPE XL XM: FILE |
| | SYSTEM ERROR nn |
| | |
| -169 | INVALID MODE FOR XM ATTACH OPTIONS |
| | |
| -170 | CANNOT OPEN ILR LOG FILE: FILE SYSTEM ERROR nn |
| | |
| -172 | CANNOT READ ILR LOG FILE: FILE SYSTEM ERROR nn |
| | |
| -173 | UNABLE TO OBTAIN WRITE ACCESS TO THE DATABASE (NEEDED FOR |
| | ILR RECOVERY) |
| | |
| -174 | THE DATABASE MUST BE OPENED IN MODE 1 - 4 SINCE ILR RECOVERY |
| | IS NECESSARY |
| | |
| -175 | CANNOT ATTACH DATA SET # decimal integer TO MPE XL XM: XM ERROR |
| | nn |
| | |
| -176 | CANNOT DETACH DATA SET # decimal integer FROM MPE XL XM: XM |
| | ERROR nn |
| | |
| -177 | USER LOG FILE IS NOT ON THE SAME VOLUME SET AS DATABASE |
| | |
| -178 | CANNOT DETACH DATA SET # decimal integerFROM MPE XL XM: FILE |
| | SYSTEM ERROR nn |
| | |
| -179 | CANNOT BEGIN MPE XL XM TRANSACTION FOR ATTACH: XM ERROR nn |
| | |
| -180 | ILR LOG INVALID - ILR INCOMPATIBLE IN MPE XL |
| | |
| -181 | ILR LOG FILE INVALID - INTERNAL GROUP NAME DOES NOT MATCH |
| | ROOT FILE |
| | |
| -182 | ILR LOG FILE INVALID - INTERNAL ACCOUNT NAME DOES NOT MATCH |
| | ROOT FILE |
| | |
| -183 | ILR LOG FILE INVALID - INTERNAL CREATION DATE DOES NOT MATCH |
| | ROOT FILE |
| | |
| -184 | ILR LOG FILE INVALID - INTERNAL LAST ACCESS DATE DOES NOT MATCH |
| | ROOT FILE |
| | |
| -187 | ILR ALREADY ENABLED FOR THIS DATABASE |
| | |
| -188 | ILR ALREADY DISABLED FOR THIS DATABASE |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| -189 | CANNOT BEGIN MPE XL TRANSACTION FOR DETACH: XM ERROR nn |
| | |
| -190 | BAD DATABASE REFERENCE OR INVALID SYSTEM DATABASE CONTROL BLOCK |
| | |
| -191 | SYSTEM DATABASE CONTROL BLOCK FULL |
| | |
| -192 | INVALID DBU |
| | |
| -193 | DBU CONTROL BLOCK IS FULL |
| | |
| -194 | INVALID DBB |
| | |
| -195 | INVALID DBG |
| | |
| -196 | DBB CONTROL BLOCK IS FULL |
| | |
| -197 | DBG CONTROL BLOCK IS FULL |
| | |
| -198 | TOTAL DBOPEN COUNT PER USER EXCEEDS LIMIT |
| | |
| -199 | CANNOT END MPE XL XM TRANSACTION: XM ERROR nn |
| | |
| -200 | DATABASE LANGUAGE NOT SYSTEM SUPPORTED |
| | |
| -201 | NATIVE LANGUAGE SUPPORT NOT INSTALLED |
| | |
| -202 | MPE NATIVE LANGUAGE SUPPORT ERROR nn |
| | RETURNED BY NLINFO |
| | |
| -204 | USER STACK IS TOO SMALL FOR RECOVERY IN DBOPEN. |
| | |
| -205 | WRONG VERSION OF DS SUBSYSTEM. |
| | |
| -206 | REMOTE TURBOIMAGE DATABASE EXCEEDS IMAGE/3000 LIMITATION |
| | |
| -208 | MPE ERROR nn RETURNED BY FLABELINFO FOR MPE XL XM |
| | |
| -209 | INVALID MODE FOR MPE XL XM DETACH |
| | |
| -210 | MPE ERROR nn WHILE GETTING LOG FILE NAME[REV BEG] |
| | |
| -211 | INVALID OR NO USER LABEL. |
| | |
| -212 | DATABASE CORRUPTION DETECTED[REV END] |
| | |
| -213 | DBXEND ENCOUNTERED XM ERROR nn WHEN ENDING DYNAMIC TRANSACTION |
| | |
| -214 | CANNOT CALL DBXUNDO WHEN A TRANSACTION IS STARTED BY DBBEGIN. |
| | |
| -215 | XM ERROR nn ENCOUNTERED WHEN ROLLING OUT DYNAMIC TRANSACTION |
| | |
| -216 | CANNOT END A DYNAMIC TRANSACTION WITH A DBEND |
| | |
| -217 | DBOPEN MODE n INCOMPATIBLE WITH DYNAMIC ROLLBACK |
| | |
| -218 | OUTPUT DEFERRED IS INCOMPATIBLE WITH DYNAMIC ROLLBACK |
| | |
| -219 | REMOTE DATABASE ACCESS IS INCOMPATIBLE WITH DYNAMIC ROLLBACK |
| | |
| -220 | DATABASE AND USER LOG NOT ATTACHED TO THE SAME XM LOG SET |
| | |
| -221 | CANNOT BEGIN A TRANSACTION WHEN A DYNAMIC TRANSACTION IS ACTIVE |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| -222 | ONLY DBXUNDO ALLOWED WHEN A DYNAMIC TRANSACTION ENCOUNTERS AN |
| | ERROR |
| | |
| -223 | CANNOT DBXEND OR DBXUNDO A TRANSACTION WHICH WAS NOT ACTIVE |
| | |
| -224 | DBCONTROL MODE 1 NOT ALLOWED INSIDE A DYNAMIC TRANSACTION |
| | |
| -225 | RECORD TABLE FULL FOR DYNAMIC ROLLBACK |
| | |
| -226 | ERROR OCCURRED WHEN CREATING THE 00 FILE |
| | |
| -227 | ERROR OCCURRED IN 00 FILE RECOVERY |
| | |
| -228 | DBXBEGIN ENCOUNTERED XM ERROR nn WHEN STARTING A DYNAMIC |
| | TRANSACTION |
| | |
| -229 | CANNOT DELETE MANUAL MASTER WITH EMPTY CHAINS. |
| | |
| -230 | A DBUNLOCK INSIDE A DYNAMIC TRANSACTION IS NOT ALLOWED |
| | |
| -231 | DURING DYNAMIC ROLLBACK RECOVERY, INTERNAL PROCEDURE FAILED; |
| | ERROR nn |
| | |
| -232 | ILLEGAL DBCLOSE MODE 2 USED DURING AN ACTIVE DYNAMIC TRANSACTION |
| | |
| -233 | KEY DATA FOUND IN THE DATABSE DOES NOT MATCH THAT IN THE MEMO |
| | RECORD |
| | |
| -234 | CANNOT PURGE THE 00 FILE |
| | |
| -235 | DYNAMIC TRANSACTION ABORTED DUE TO DBCLOSE MODE 1; DATABASE |
| | CLOSED |
| | |
| -236 | INTERNAL ERROR OCCURRED WHEN OPENING THE AUX FILE; ERROR nn |
| | |
| -237 | CANNOT DBXEND OR DBXUNDO A DBBEGIN TRANSACTION [REV BEG] |
| | |
| -238 | MDBX, MODES OF DBXBEGIN/DBXEND DON'T MATCH. |
| | |
| -240 | ERROR IN DYNAMIC ROLLBACK. |
| | |
| -241 | BAD TAG FOR TURBOLKT TABLE. |
| | |
| -242 | ERROR IN TURBOGTX FILE OPERATION. |
| | |
| -243 | INVALID DYNAMIC ROLLBACK TRANSACTION ID. |
| | |
| -244 | BASE COUNT OVER 15 FOR DMDBX. |
| | |
| -245 | OUT OF SPACE FOR TURBOGTX FILE. |
| | |
| -246 | ERROR IN TURBOGTX OPERATION RELATED TO ATC TRANSACTION. |
| | |
| -250 | CBINIT FAILED ON nn |
| | |
| -251 | DBS WAS OBTAINED BUT NOT RELEASED.[REV END] |
| | |
| -253 | DATABASE ENABLED FOR INDEXING, BUT THIRD-PARTY INDEXING IS NOT |
| | CONFIGURED |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| -254 | ROLLBACK OF THIRD-PARTY INDEX FAILED; INDEXING DISABLED FOR DATA |
| | SET |
| | |
| -255 | THIRD-PARTY INDEXING DISABLE FAILED; INDEXING DISABLED FOR |
| | DATABASE |
| | |
| -256 | THIRD-PARTY INDEX FOR PATH decimal integer: nn IS FULL |
| | |
| -257 | THIRD-PARTY INDEX FOR PATH decimal integer: nn IS DAMAGED |
| | |
| -258 | INVALID ARGUMENT FOR INDEX |
| | |
| -259 | INVALID MODE FOR INDEX |
| | |
| -260 | NO PREVIOUS LIST OF QUALIFIED DATA ENTRIES[REV BEG] |
| | |
| -261 | DYNAMIC PROCEDURE LOAD ERROR FOR INTRINSIC ROLLBACK. |
| | |
| -262 | OLDER/INCOMPATIBLE VERSION OF IMAGE/SQL. |
| | |
| -263 | INVALID PCODE RETURNED BY TPI. |
| | |
| -264 | WRITE ERROR FOR TPI FILES. |
| | |
| -265 | ERROR IN THIRD-PARTY SHADOWING PACKAGE. |
| | |
| -266 | ERROR WHILE DISABLING THIRD-PARTY SHADOWING. |
| | |
| -267 | DAMAGED FILE ERROR RETURNED BY THIRD-PARTY SHADOWING. |
| | |
| -268 | INVALID PCODE RETURNED BY TPS. |
| | |
| -269 | WRITE ERROR FOR TPS FILES.[REV END] |
| | |
| -3nn | INTERNAL TURBOIMAGE ERROR RETURNED (#n)[REV BEG] |
| | |
| -305 | INVALID DATA SET NUMBER. |
| | |
| -306 | INVALID DATA SET TYPE. |
| | |
| -307 | INVALID RECORD NUMBER FOUND. |
| | |
| -308 | ERROR RELATED TO BEGINNING OF FILE. |
| | |
| -309 | BUFFER IO NOT YET COMPLETE. |
| | |
| -310 | ERROR RELATED TO END OF FILE. |
| | |
| -312 | INTERNAL ERROR ENCOUNTERED WHILE READING DATABASE BLOCK. |
| | |
| -314 | ERROR WHILE OBTAINING PATH INFORMATION FOR SET. |
| | |
| -322 | INTERNAL TURBOIMAGE ERROR RETURNED nn |
| | |
| -323 | UNEXPECTED EMPTY RECORD FOUND. |
| | |
| -331 | DSET CAPACITY INFORMATION NOT CURRENT. |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| -332 | ERROR IN QLOCK OPERATION. |
| | |
| -333 | ERROR IN QOPEN OPERATION. |
| | |
| -420 | FEATURE NOT IMPLEMENTED.[REV END] [REV BEG] |
| | |
| -421 | BTE:UNKNOWN QUALIFIER VALUE FOR DBCONTROL MODE 13. |
| | |
| -422 | BTE: DATA SET # NOT IN VALID RANGE. |
| | |
| -423 | BTE: B-TREE ALREADY EXISTS. |
| | |
| -424 | MESSAGE\BTE: FAILED TO CREATE B-TREE. |
| | |
| -425 | MESSAGE\BTE: DB NOT OPENED EXCLUSIVELY. |
| | |
| -426 | BTE: B-TREE DOESN'T EXIST. |
| | |
| -427 | BTE: FCLOSE, PURGE FAILED. |
| | |
| -428 | BTE: REBUILDINDEX FAILED. |
| | |
| -429 | BTE: DBFIND ARGUMENT VERSION IS BAD. |
| | |
| -430 | BTE: DBFIND (mode 4/24) ARGUMENT TYPE IS BAD. |
| | |
| -431 | BTE: DBFIND (mode 4/24) ARGUMENT #1 LENGTH IS BAD. |
| | |
| -432 | BTE: WILDCARD NOT ASCII. |
| | |
| -433 | BTE: DBFIND (MODE 4/24) ARGUMENT #2 LENGTH IS BAD. |
| | |
| -434 | DATASET DETAIL INSTEAD OF MASTER. |
| | |
| -436 | BTE: FAILED TO EXTRACT DATA FROM ROOT FILE. |
| | |
| -437 | BTE: FAILED TO CONVERT @c TO [] DBFIND. |
| | |
| -438 | BTE: BAD ITEM # IN INIT BTREE. |
| | |
| -439 | BTE: CONVERSION OF KEY FROM EXTERNAL TO INTERNAL FORMAT FAILED. |
| | |
| -440 | BTE: XM ATTACH OF INDEX FILE FAILED. |
| | |
| -441 | BTE: XM DETACH OF INDEX FILE FAILED. |
| | |
| -442 | BTE: RELEASE OF INDEX FILE FAILED. |
| | |
| -443 | BTE: SECURE OF INDEX FILE FAILED. |
| | |
| -444 | BTE: DBFIND ON NON-KEY FIELD OF MASTER.[REV END] |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
-----------------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
-----------------------------------------------------------------------------------------------------
| [REV BEG] | |
| | |
| -446 | BTE: ARGUMENT 2 SPECIFIED FOR RELOP OF (</<=/=/>=/>). |
| | |
| -447 | BTE: FAILED TO BUILD RECORD HOLDING ROOT DATA INFORMATION. |
| | |
| -448 | BTE: FAILED TO SETUP INFORMATION FOR USERLABEL 0 OF DATASET. |
| | |
| -449 | BTE: FAILED TO POSITION INDEX AT START OF KEY RANGE. |
| | |
| -451 | BTE: ROOT VERSION LESS THAN "C4". |
| | |
| -452 | BTE: KEY LENGTH GREATER THAN 252 BYTES (MAXIMUM INDEX KEY SIZE). |
| | |
| -458 | DBOPEN FAILED. OUT OF DISK SPACE[REV END] |
| | |
| -1000 | SWITCH TO NM FAILED ON intrinsic name, INFO nn SUBSYS nn |
| | |
| -1001 | SWITCH TO CM FAILED ON CX'PCBXIMAGE |
| | |
| -1002 | HPLOADCMPROCEDURE FAILED ON CX'PCBXIMAGE |
| | |
| -1003 | SWITCH TO NM FAILED ON intrinsic name, INFO nn SUBSYS nn |
| | |
| -1004 | HPLOADNMPROC FAILED ON CM intrinsic name[REV BEG] |
| | |
| -3999 to -3000 | ERROR RETURNED BY THIRD-PARTY INDEXING PRODUCTS.[REV END] |
| | |
| 10 | BEGINNING OF FILE |
| | |
| 11 | END OF FILE |
| | |
| 12 | DIRECTED BEGINNING OF FILE |
| | |
| 13 | DIRECTED END OF FILE |
| | |
| 14 | BEGINNING OF CHAIN |
| | |
| 15 | END OF CHAIN |
| | |
| 16 | THE DATA SET IS FULL |
| | |
| | (The following messages are returned only if capacity expansion |
| | is specified for the data set. Dataset# and FSERR # are |
| | replaced by the actual number.) |
| | |
| | DBPUT CANNOT EXPAND dataset#: DATA SET AT MAXIMUM CAPACITY |
| | |
| | DBPUT dataset# INCOMPLETE EXPANSION: FILE SYSTEM ERROR # |
| | |
| | DBPUT CANNOT EXPAND dataset#: OUT OF DISC SPACE (FSERR #) |
| | |
-----------------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| 17 | THERE IS NO CHAIN FOR THE SPECIFIED SEARCH ITEM VALUE |
| | THERE IS NO ENTRY WITH THE SPECIFIED KEY VALUE |
| | THERE IS NO PRIMARY SYNONYM FOR THE SPECIFIED KEY VALUE |
| | NO CURRENT RECORD OR THE CURRENT RECORD IS EMPTY (CONTAINS |
| | NO ENTRY) |
| | THE SELECTED RECORD IS EMPTY (CONTAINS NO ENTRY) |
| | |
| 18 | BROKEN CHAIN - FORWARD AND BACKWARD POINTERS |
| | NOT CONSISTENT |
| | |
| 20 | DATABASE CURRENTLY LOCKED |
| | SETS OR ENTRIES LOCKED WITHIN DATABASE |
| | |
| 22 | DATA SET ALREADY LOCKED |
| | |
| 23 | CANNOT LOCK SET DUE TO LOCKED ENTRIES WITHIN IT |
| | (Conditional Locks Only) |
| | |
| 24 | ENTRIES CURRENTLY LOCKED USING DIFFERENT ITEM |
| | (Conditional Locks Only) |
| | |
| 25 | CONFLICTING DATA ENTRY LOCK ALREADY IN EFFECT |
| | |
| 26 | IMMINENT DEADLOCK. |
| | |
| 41 | DBUPDATE ATTEMPTED TO MODIFY VALUE OF CRITICAL ITEM--KEY, SEARCH |
| | OR SORT |
| | |
| | (The following messages are returned only if the critical item |
| | update (CIUPDATE) option is permitted for the database and the |
| | current process. The bracketed numbers after the messages refer |
| | to the value in halfword 3 of the status array. The nn in the |
| | value represents the path number returned.) |
| | |
| | DBUPDATE: NO CHAIN HEAD (MASTER ENTRY) FOR |
| | PATH decimal integer: nn [1nn] |
| | DBUPDATE: FULL CHAIN FOR PATH decimal integer: nn |
| | (CONTAINS 2,147,483,647 ENTRIES) [2nn] |
| | |
| | DBUPDATE: FULL AUTOMATIC MASTER FOR PATH decimal integer: nn |
| | [3nn] |
| | |
| | DBUPDATE: FULL AUTOMATIC MASTER SYNONYM CHAIN FOR |
| | PATH decimal integer: nn [4nn] |
| | |
| 42 | DBUPDATE WILL NOT ALTER A READ-ONLY DATA ITEM |
| | |
| 43 | DUPLICATE KEY VALUE IN MASTER |
| | |
| 44 | CAN'T DELETE A MASTER ENTRY WITH NON-EMPTY DETAIL CHAINS |
| | |
| 49 | ILLEGAL BUFFER ADDRESS |
| | |
| 50 | USER'S BUFFER IS TOO SMALL FOR REQUESTED DATA (only returned if |
| | buffer is too small and the data transfer would write over in |
| | the user's stack) |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBERROR Messages (cont.)
--------------------------------------------------------------------------------------------
| | |
| Return Status | DBERROR Message |
| | |
--------------------------------------------------------------------------------------------
| | |
| 51 | STACK OVERFLOW FOR BASIC - IMAGE INTERFACE. |
| | |
| 52 | INVALID PARAMETER FOR BASIC - IMAGE INTERFACE. |
| | |
| 53 | INVALID PARAMETER TYPE FOR BASIC - IMAGE INTERFACE. |
| | |
| 60 | DATABASE ACCESS DISABLED |
| | |
| 61 | PROCESS HAS THE DATABASE OPEN 63 TIMES; |
| | NO MORE ALLOWED |
| | |
| 62 | DBG CONTROL BLOCK FULL |
| | |
| 63 | DBG DISABLED; POTENTIAL DAMAGE; ONLY DBCLOSE ALLOWED |
| | |
| 64 | NO ROOM FOR DBG ENTRY IN PCBX (MPE PORTION OF STACK) |
| | |
| 65 | CAN'T GRANT BUFFER REQUEST. |
| | |
| 66 | DBG POINTED TO BY ROOT FILE DOES NOT MATCH |
| | |
| 67 | DBU DISABLED; POTENTIAL DAMAGE; ONLY DBCLOSE ALLOWED |
| | |
| 68 | DBB DISABLED; POTENTITIAL DAMAGE; ONLY DBCLOSE |
| | ALLOWED |
| | |
| 69 | BAD DATABASE (if database does not close normally and AUTODEFER |
| | is active) |
| | |
| 71 | LOGGING NOT ENABLED FOR USER. |
| | |
| 72 | TURBOLKT TABLE FULL. |
| | |
| 73 | ERROR IN TURBLKT TABLE OPERATION. |
| | |
| 1nn | NO CHAIN HEAD (MASTER ENTRY) FOR PATH decimal integer: nn |
| | |
| 2nn | FULL CHAIN FOR PATH decimal integer: nn |
| | (CONTAINS 2,147,483,647 ENTRIES) |
| | |
| 3nn | FULL AUTOMATIC MASTER FOR PATH decimal integer: nn |
| | |
| 4nn | FULL AUTOMATIC MASTER SYNONYM CHAIN FOR |
| | PATH decimal integer: nn |
| | |
| 944 | WARNING: ASSUMING NO MESSAGE CATALOG |
| | |
| 3000--3999 | ERRORS RETURNED BY THIRD-PARTY INDEXING PRODUCTS |
| | |
| Others | UNRECOGNIZED RETURN STATUS: decimal integer |
| | |
--------------------------------------------------------------------------------------------
DBEXPLAIN
INTRINSIC NUMBER 418.
Prints a multiline message on the $STDLIST device describing a
TurboIMAGE/XL procedure call and explaining the call's results as
recorded in the calling program's status array.
Syntax.
DBEXPLAIN,status
Parameters.
status is the name of the array used as the status
parameter in the TurboIMAGE/XL procedure call about
which information is requested.
NOTE The call to DBEXPLAIN must be made immediately after receiving an
error status before any other intrinsics are executed to ensure the
display of valid messages.
Discussion.
Table 5-11 contains the general format for lines 2 through 6 of the
message which is sent to $STDLIST. Elements surrounded by brackets are
sometimes omitted. Braces indicate that only one of the choices shown
will be printed. Lines 5 and 6 are printed only if, during the
preparation of lines 2, 3, and 4, TurboIMAGE/XL detects that the status
array contents are invalid, unrecognizable, or incomplete, or if a
message must be truncated to fit on a single line.
If the status array contents appear to be the result of something other
than a TurboIMAGE/XL procedure call or if the array is used by the called
procedure for information other than that discussed here, the second
choice for line 3 is printed. This would be the case for a successful
call to DBGET which uses all 10 status elements to return a return
status, lengths, and record numbers.
If the status array contains an unrecognized error code, the second line
4 choice is printed. If the return status is greater than or equal to
zero, the word ERROR in line 2 is replaced by RESULT because non-negative
return statuses indicate success or exceptional conditions, such as
end-of-chain. Return status values are explained in appendix A.
You can use the offset information to locate the specific call statement
that generated the status array contents if the call is made with a
programming language which enables you to determine displacements of
program statements or labels within the code. The identity of the code
segment is not printed because it cannot be determined by DBEXPLAIN.
Therefore, you need to be familiar with the program's functioning in
order to locate the correct call. The offset portion of line 2 is
printed only if the status array appears to be set by a TurboIMAGE/XL
library procedure call and contains valid offset information.
Table 5-11. DBEXPLAIN Message Format
--------------------------------------------------------------------------------------------
| | |
| Line | Format |
| | |
--------------------------------------------------------------------------------------------
| | |
| 1 | (a blank line) |
| | |
| | |
| | |
| 2 | |
| | TurboIMAGE { ERROR } [ AT offset] RETURN STATUS=retstat |
| | { RESULT} |
| | |
| | |
| 3 | |
| | { intrinsicname,MODE x,ON [ setname OF] basename} |
| | { [ ;PASSWORD=password] } |
| | { TurboIMAGE CALL INFORMATION NOT AVAILABLE } |
| | |
| | |
| 4 | |
| | { message } |
| | { UNRECOGNIZED RETURN STATUS: retstat} |
| | |
| | |
| 5 | |
| | [ HEX DUMP OF STATUS ARRAY FOLLOWS ] |
| | [ OCTAL DUMP OF STATUS ARRAY FOLLOWS] |
| | |
| | |
| 6 | |
| | [ hex display ] |
| | [ octal display] |
| 7 | (a blank line) |
| | |
--------------------------------------------------------------------------------------------
| | |
| Parameter | Explanation |
| | |
--------------------------------------------------------------------------------------------
| | |
| offset | The code offset of the TurboIMAGE/XL procedure call in a CM |
| | procedure. It is the virtual memory address of the TurboIMAGE/XL |
| | procedure call in a NM procedure. |
| | |
| retstat | The return status (from the first element of status) printed as a |
| | decimal integer and corresponding to the return statuses described in |
| | appendix A. |
| | |
| intrinsicname | The name of the TurboIMAGE/XL library procedure (intrinsic) which was |
| | called and which sets the contents of the status array. |
| | |
| x | The value of the mode parameter as a decimal integer. |
| | |
| setname | The value of the second parameter, usually a data set name or number, |
| | as passed to the procedure which set the status array contents. The |
| | second parameter can be a data item name or number if the procedure |
| | in question is DBINFO. If the procedure is DBOPEN, DBLOCK, DBUNLOCK, |
| | or certain modes of DBINFO or DBCLOSE, setname is omitted. |
| | |
| password | The word printed at the end of line 3 only if the error relates to |
| | the password parameter of DBOPEN. |
| | |
| basename | The database specified in the procedure which was called and set the |
| | status array contents. |
| | |
--------------------------------------------------------------------------------------------
Table 5-10. DBEXPLAIN Message Format (Continued)
--------------------------------------------------------------------------------------------
| | |
| Parameter | Explanation |
| | |
--------------------------------------------------------------------------------------------
| | |
| message | A description of the result based on the condition word and other |
| | status array information. The message is generated by the DBERROR |
| | procedure which is also described in this chapter. See Table 5-9 for |
| | all possible messages returned in line 4. |
| | |
| hex display | A listing of each halfword of status printed as a string of 4 hex |
| | digits. Adjacent status elements are separated by a blank and the |
| | entire line is 49 characters long. The hex display is generated for |
| | NM applications only. |
| | |
| octal display | A listing of each halfword of status printed as a string of 6 octal |
| | digits. Adjacent status elements are separated by a blank and the |
| | entire line is 49 characters long. The octal display is generated |
| | for CM applications only. |
| | |
--------------------------------------------------------------------------------------------
Figure 5-1 contains four examples of messages generated by DBEXPLAIN
for a Native Mode application.
________________________________________________________________________________
| |
| TURBOIMAGE RESULT AT $0001d76c: RETURN STATUS=0 DBOPEN=intrinsic name |
| DBOPEN,MODE1, ON ORDERS ORDERS=database name |
| SUCCESSFUL EXECUTION - NO ERROR NO ERROR=message |
| |
| TURBOIMAGE ERROR AT $0001d76c: RETURN STATUS=-12 |
| DBPUT,MODE1, ON DATE-MASTER OF ORDERS DATE-MASTER=data set name|
| DBPUT CALLED WITHOUT COVERING LOCK IN EFFECT |
| |
| TURBOIMAGE RESULT AT $0001d76c: RETURN STATUS=16 |
| DBPUT,MODE1, ON #1 OF ORDERS #1=data set number |
| THE DATA SET IS FULL |
| |
| TURBOIMAGE RESULT: RETURN STATUS=4792 |
| TURBOIMAGE CALL INFORMATION NOT AVAILABLE |
| UNRECOGNIZED RETURN STATUS: 4792 |
| HEX DUMP OF STATUS ARRAY FOLLOWS: |
| 12b8 0040 0c63 ff82 4d33 02a7 32e8 0000 0000 0000 |
| ...............hex display................... |
________________________________________________________________________________
Figure 5-1. Sample DBEXPLAIN Messages
Because the application is in Native Mode, the display is in hex. For
Compatibility Mode applications, the display is in octal.