The response codes are listed in ascending order:
ERRI=N/A
Database processing completed with no errors.
ERRI=N/A
Record with requested key or RID not found (GET/UPD/DEL), OR reposition RID not in scan result list (SEQ RESET).
ERRI=N/A
End of file on GET sequential (forward or backward).
ERRI=field name
Named field not found for INFO on field name.
ERRI=N/A
No records found for supplied SCAN criteria.
ERRI=N/A
SCAN terminated-exceeded I/O limit.
ERRI=N/A
SCAN terminated-exceeded time limit.
ERRI=N/A
SCAN terminated-exceeded storage limit.
ERRI=N/A
SCAN terminated-met or exceeded number of records limit.
ERRI=N/A
Linked &NDBGET/&NDBFMT-extra no find return code as used in the link definition.
ERRI=format name
FMT del, format name not found.
ERRI=sequence name
SEQ del, sequence not found.
ERRI=N/A
Maximum possible Important! code-currently not assigned.
ERRI=N/A
Error in request (catch-all). See command/messages.
ERRI=N/A
Logic error in request: not signed on to database (NDB). For example, if the NCL procedure is paused and the database stopped/started, then the next call gets this error.
ERRI=N/A
Insufficient storage to process request.
ERRI=N/A
OPEN request rejected, database is stopping.
ERRI=N/A
&NDBOPEN-already open to this NDB.
ERRI=N/A
&NDBCLOSE-not open to this NDB.
ERRI=N/A
NDB PURGE-nominated NDB not found, could not purge.
ERRI=N/A
NDB PURGE-nominated NDB not locked, cannot purge.
ERRI=N/A
Load for load module for requested NDB function failed.
ERRI=N/A
Requested option not allowed-NDB is in load mode.
ERRI=N/A
&NDBOPEN failed by NCLEX01 user exit.
ERRI=N/A
This &NDB... verb blocked by &NDBOPEN user exit (NCLEX01) return mask.
ERRI=N/A
Database open failure: VFS open for database failed.
Possible causes:
ERRI=N/A
Database open failure: Specified database name is not a VSAM KSDS.
ERRI=N/A
Database open failure: VSAM relative key position (RKP) not 0.
ERRI=N/A
Database open failure: VSAM key length too short (that is, fewer than 16) to be a valid NDB database.
ERRI=N/A
Database open failure: VSAM data length too short to be a valid NDB database.
ERRI=N/A
Database open failure: Read of control record failed.
ERRI=N/A
Database open failure: Control record not valid.
ERRI=N/A
Database open failure: Unable to get storage to contain control record.
ERRI=N/A
Database open failure: Read of transaction control record failed.
ERRI=N/A
Database open failure: Transaction control record not valid.
ERRI=N/A
Database open failure: Unable to get storage to contain transaction control record.
ERRI=N/A
Database open failure: Unable to get storage to contain transaction data record.
ERRI=N/A
Database open failure: Error building field name indexes.
ERRI=N/A
Database open failure: Error re-applying pending transaction. Probable file full condition.
ERRI=N/A
Database open failure: Database flagged as in DEFER status. Probable file corrupt condition, system has failed with database started in DEFER mode.
ERRI=N/A
Database open failure: UDB is open by other users.
ERRI=N/A
UDB is open INPUT and NDB START or &NDBOPEN is not for INPUT only mode.
ERRI=N/A
Domain ID on NDB control record and this system mismatch, and FORCE not on NDB START. NDB is not started. Important!-it might be currently open in another system.
ERRI=N/A
NDB version in this NDB control record not supported.
ERRI=N/A
This NDB is open under another file ID on this system (VSAM timestamp match).
ERRI=N/A
Request not allowed on active database. For example, NDB CREATE, NDB RESET, NDB ALTER, or NDB UNLOAD.
ERRI=N/A
User ID required for request. Internal failure, should never occur with NDB command.
ERRI=sequence name
Specified sequence name not defined.
ERRI=sequence name
Sequence name required or already defined.
ERRI=N/A
Free-format text had an invalid token:
ERRI=N/A
Logic error-not signed on to database (NDB). For example, if NCL proc is paused, and DB stopped/started, then next call will get this error.
ERRI=N/A
This user ID has an asynchronous request running. Internal failure; should never occur with NDB command or &NDB statements.
ERRI=N/A
Request internally canceled.
ERRI=N/A
OPEN EXCLUSIVE-other users on database.
ERRI=N/A
OPEN-database locked by an exclusive user.
ERRI=field name if relevant
Add, update, or delete field, an error in the field list syntax, and so on.
ERRI=N/A
Add, update, or delete field, an internal error in the field index.
ERRI=field name
Value for named field is bad, not recognizable as valid data.
ERRI=field name
Value for named field is too long.
ERRI=field name
Value for named numeric field is not numeric, or outside range:
-2,147,483,648 : 2,147,483,647.
ERRI=field name
Value for named hexadecimal field is not a valid hexadecimal string, or is an odd number of characters.
ERRI=field name
Value for named DATE or CDATE field is not valid.
ERRI=field name
Field name is not a valid floating point number.
ERRI=field name
Supplied value is not a valid hexadecimal number.
ERRI=field name
Value for named time field is not a valid time, in the format:
HHMMSS or HHMMSS.TTTTTT.
ERRI=N/A
Operation not allowed. NDB or user open in input-only mode.
ERRI=field name
Field update request-could not read field record from NDB.
ERRI=field name
Supplied value is not a valid timestamp, in the format:
YYYYMMDDHHMMSS.TTTTTT.
ERRI=token in error
ADD or UPD, field=value list syntax error.
ERRI=field name
ADD or UPD, required field not provided.
ERRI=field name
ADD record, sequence key value already on database (that is, not unique).
ERRI=field name
ADD/UPD record, KEY=UNIQUE field value not unique.
ERRI=field name
UPD record, UPDATE=NO value change for field.
ERRI=format name
Format specified on an ADD or UPD does not exist.
ERRI=format name
Format specified on an ADD or UPD exists but is an INPUT format and cannot be used for output.
ERRI=format name
FMT add, format name '*' is invalid.
ERRI=format name
FMT add, format name already exists.
ERRI=token in error
FMT/GET, format list syntax error.
ERRI=field name
FMT/GET, field name not defined in database.
ERRI=format name
Format specified on a GET exists but is an OUTPUT format and cannot be used for input.
ERRI=field name
You have referenced an NDB field twice in an OUTPUT format definition.
ERRI=field name
You have used an NCL keyword name in an OUTPUT format, but the keyword is not an NCL system variable name.
ERRI=format name
GET, supplied format name not defined.
ERRI=field name
GET by key, key field not defined on database.
ERRI=field name
GET by key, field not keyed.
ERRI=sequence name
GET by sequence, sequence ID not defined.
ERRI=sequence name
GET by sequence, key field for sequence has been deleted (by &NDBDEF DELETE).
ERRI=sequence name
GET by sequence, skip=0 specified and not currently positioned.
ERRI=sequence name
GET by sequence, skip=0 specified and currently at EOF (front or back).
ERRI=field name
GET by key field, GENERIC= is invalid for this field format. Generic access is only allowed for character and HEX fields.
ERRI=field name
&NDBGET histogram (KEY=) on sequence key not supported.
ERRI=sequence name
SEQ DEF-invalid sequence name.
ERRI=sequence name
SEQ DEF, sequence name already exists.
ERRI=N/A
SEQ DEF, from or to RID invalid.
ERRI=sequence name
SEQ DEF, field name not found or is not a key.
ERRI=N/A
SEQ DEF, from or to values not valid.
ERRI=field name
SEQ DEF, generic invalid with field format.
ERRI=N/A
SEQ DEF, invalid null value for GENERIC=.
ERRI=sequence name
SEQ RESET, sequence not found.
ERRI=invalid data value
SEQ RESET, REPOS= value invalid or null.
ERRI=N/A
SEQ RESET, REPOS= not valid on a scan sequence that is not sorted, or, while sorted, the primary sort field was substringed.
ERRI=sequence name
SEQ RESET, REPOS by RID only valid for a SCAN sequence.
ERRI=N/A
&NDBSEQ histogram (KEY=) on sequence key not supported.
ERRI=sequence name
RELPOS sequence is not a sequence constructed by &NDBSCAN.
ERRI=N/A
INFO by field number, number lt 1 or gt number fields in database.
ERRI=sequence name
SCAN sequence ID is already defined.
ERRI=sequence name
SCAN sequence ID is currently in use, by an active scan for this user.
ERRI=field name
SCAN SORT= field name not defined on database.
ERRI=N/A
SCAN syntax error in scan request.
ERRI=N/A
Unload failed. Accompanying messages will indicate the cause of the failure
ERRI=N/A
NDB ALTER failed.
ERRI=N/A
File integrity error, get if continuation DBDR failed. Database possibly corrupted. Contact Technical Support.
ERRI=field name
File integrity error, get XFF if DBKR failed. Database possibly corrupted. Contact Technical Support.
ERRI=field name
File integrity error, get KGE if DBKR failed. Database possibly corrupted. Contact Technical Support.
ERRI=N/A
VSAM I/O Error. See log for more information.
ERRI=N/A
Request not processed-invalid request code (internal error), should never occur with NCL (&NDB) or NDB command.
ERRI=N/A
Request not processed-RPL busy flag set (internal error), should never occur with NCL (&NDB) or NDB command.
ERRI=N/A
Request not processed-insufficient storage to queue request to database handler. Try again.
ERRI=N/A
Request not processed-required text parameter not provided (internal error). Should never occur with NCL (&NDB) or NDB command.
ERRI=N/A
Request not processed-Database not started.
ERRI=N/A
Request not processed-required VAL1 parameter not provided (internal error). Should never occur with NCL (&NDB) or NDB command.
ERRI=N/A
Request not processed-required VAL2 parameter not provided (internal error). Should never occur with NCL (&NDB) or NDB command.
ERRI=N/A
Request not processed-database not LOCKED. Only applicable to NDB START UNLOCK command.
ERRI=N/A
Request not processed-database is LOCKED or STOPPING.
ERRI=N/A
Request not processed-long running command currently in progress. For example, NDB UNLOAD.
ERRI=abend code
This return code indicates that an NDB operation was terminated due to a logical abend caused by a possible NDB corruption. The log will contain useful debugging information.
For update requests, the NDB will be stopped and locked. For read/scan requests, the request is terminated but the NDB will continue to process other requests.
ERRI=N/A
Request not processed-feature not present, or your product is shutting down.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |