| Text | ISN list not sorted. DB/FNR .../... Subcode .... |
| Expl. | An ISN list could not be sorted because of either an excessive number of resulting ISNs or a discrepancy between the number of ISNs returned and the actual number of records found (the latter is only possible only if "security by value" is being used). For the detailed reason see the subcode. |
| Actn. | Reduce number of ISNs in SORT. |
| Text | Record not held. DB/Subcode .../.... |
| Expl. | ISNs could not be held because of insufficient space in the hold
queue. |
| Actn. | Contact your database administrator. |
| Text | End-of-file or end-of-list detected. DB/FNR .../.... |
| Expl. | An end-of-file or end-of-list condition was detected, or a program tried to read/change a multi-client file"s record using an owner ID which was blank, incorrect or not allowed for the record. |
| Actn. | For more information, please refer to the Adabas documentation. |
| Text | Sx command interrupted due to time limit. DB/FNR .../.... |
| Expl. | An Sx command has been interrupted because the maximum amount of
time permitted has been exceeded. |
| Actn. | Contact your database administrator. |
| Text | Command interrupted to prevent WORK overflow. DB/FNR .../.... |
| Expl. | The command was interrupted to prevent a WORK overflow because of a pending backout operation. |
| Actn. | The value specified for the LP parameter might have to be increased. |
| Text | Last transaction backed out of database .... Subcode .... |
| Expl. | The last transaction has been backed out by Adabas because an
Adabas time limit has been exceeded or because of a security violation. This error may also occur if an Adabas OP command is required (Adabas parameter OPENRQ=YES) but an Adabas command was issued without an OP command having been issued before. For the detailed reason see the subcode. |
| Actn. | Correct cause of time-out or security violation, and execute
transaction again; or issue OP command correctly. |
| Text | Too many occurrences for periodic group. DB/FNR .../.... |
| Expl. | Too many occurrences for a periodic group. |
| Actn. | Check program and correct error. |
| Text | An error occurred in an MC call processing. DB/FNR .../.... |
| Expl. | An error occurred in an MC call during subcommand processing. |
| Actn. | Contact your database administrator. |
| Text | Invalid file number. DB/FNR .../.... Subcode .... |
| Expl. | The file number was invalid. Possible causes are: - The file number was either 0 or greater than 255. - The file was not in the database. - The file was locked. - A required Adabas system file was not loaded. For the detailed reason, see the subcode. |
| Actn. | Make sure that you use the correct file number. |
| Text | Incorrect usage of file number. DB/FNR .../.... |
| Expl. | The file number was modified between successive L2/L5 calls. |
| Actn. | Check program and correct error. |
| Text | Update not permitted for access-only file. DB/FNR .../.... |
| Expl. | An attempt was made to update a file which was opened for access
only. |
| Actn. | Check program and correct error. |
| Text | Incorrect entry made for a CID value. DB/FNR .../.... |
| Expl. | One of the following incorrect entries was used for a CID value: - X"00000000" - X"40404040" - X"FFxxxxxx" |
| Actn. | Check program and correct error. |
| Text | An invalid CID value was detected. DB/FNR .../.... Subcode .... |
| Expl. | A time-out occurred because a command ID was not found. This program error can be caused by: - the CMD ID being assigned to another Ln command (n = 1,...9); - the CMD ID being assigned to another file; - the CMD ID not found for an S8 command. |
| Actn. | Check program and correct error. |
| Text | Invalid command .... DB/FNR .../.... Subcode .... |
| Expl. | The command is invalid. A subcode appears in the Additions 2
field of the Adabas control block, the low-order (rightmost) two bytes indicating the specific cause and action for this response code. See the documentation for the subcodes. When the LNCSTUB module is used, this response code may indicate problems with the initial call (IC) to the Adabas CICS command- level link component. If the Adabas control block shows a command code of "IC", the link routine being used may not be at the proper release level or may not be the command-level version. |
| Actn. | Check program and correct error. |
| Text | Invalid starting ISN specified. DB/FNR .../.... |
| Expl. | The starting ISN specified for an L2/L5 command sequence was
invalid: - The ISN is not assigned to a record in the file. - The ISN was greater than the MAXISN in effect for the file. |
| Actn. | Check program and correct error. |
| Text | Invalid ISN in complex FIND SORTED statement. DB/FNR .../.... |
| Expl. | This error may be caused by one of the following: - The ISN list in the ISN buffer was already sorted. - The ISN list in the ISN buffer contained an invalid ISN. - The "D" option was specified when trying to sort by ISN. |
| Actn. | Check program and correct error, or contact your database administrator. |
| Text | ISN in ISN lower limit for S1/S4 not found. DB/FNR .../.... |
| Expl. | The ISN specified in ISN Lower Limit for an S1/S4 (or S2/S9)
command was not found. |
| Actn. | Check program and correct error. |
| Text | Invalid ISN buffer length. DB/FNR/Subcode .../.../.... |
| Expl. | An invalid ISN buffer length for an S9 command was detected. The number of ISNs to be sorted as provided in ISN quantity is zero, or the ISN buffer of the S9 command contains ISNs that are higher than the TOP-ISN of the file. |
| Actn. | Check program and correct error. |
| Text | Search/value buffer overflow. DB/FNR/Subcode .../.../.... |
| Expl. | There was not enough work space available to either accommodate
the combined sizes of the search and value buffers as indicated in the fields Search Buffer Length and Value Buffer Length, or generate the format translation. |
| Actn. | Check program and correct error. |
| Text | Incorrect descriptor .... DB/FNR .../.... |
| Expl. | A descriptor was invalid for an L3/L6 or S2/S9 command, because: - The field was not a descriptor. - The descriptor was changed between successive calls. - The descriptor is contained within a periodic group. - The Additions 1 field contained a different descriptor than the descriptor contained in the search buffer. |
| Actn. | Check program and correct error. |
| Text | Incorrect value repositioning attempted. DB/FNR .../.... |
| Expl. | A value repositioning was attempted with an L3/L6 command (bytes
7-8 of the Additions 1 field contain spaces) and the Command Option 2 field did not contain the value "V". The command ID is released. |
| Actn. | Check program and correct error. |
| Text | Adabas error due to invalid command option.DB/FNR .../.... |
| Expl. | An invalid command option has been detected for the database ID / file number indicated in the error message. |
| Actn. | Either remove the invalid command option or replace it with a
valid option. See the Adabas documentation for more information. |
| Text | Invalid function for non-cluster Adabas nucleus. DB/FNR .../.... |
| Expl. | The user/DBA attempted to perform a function for a non-cluster
Adabas nucleus that is available only for an Adabas cluster database. |
| Actn. | Do not perform this function for this type of nucleus. |
| Text | Syntax error detected in format buffer. DB/FNR .../.... |
| Expl. | The syntax error may be one of the following: - The terminating period was missing. - The first position contains a period. - Length and/or format was specified with a range definition. - An invalid element was detected. - The L9 descriptor name in the search buffer did not agree with the name in the format buffer. |
| Actn. | Check program and correct error. |
| Text | Error in format buffer. DB/FNR/Subc/field .../.../.../.... |
| Expl. | This error may be caused by one or more of the following: - A phonetic descriptor was specified. - A field was specified incorrectly. - An index for a periodic group or multiple-value field was specified incorrectly. - A periodic group was referenced incorrectly. - A count was specified for a field which is not a multiple-value field. - A multiple-value field was indexed incorrectly. For the detailed reason, see the subcode. |
| Actn. | Check program and correct error. |
| Text | Internal buffer too small. DB/FNR/Subcode .../.../.... |
| Expl. | A space problem occurred. The following are the subcodes and
their meanings: 1 The Work pool was too small to store a user format. 2 The internal format buffer was too small to store a user format (translated into internal structure). |
| Actn. | Subcode 1: Increase the LWP specification and retry. Subcode 2: Increase the LFP specification and retry. |
| Text | Descriptor in format and search buffer not equal. DB/FNR .../.... |
| Expl. | The descriptor specified in the format buffer did not agree with
the descriptor specified in the search buffer. |
| Actn. | Check program and correct error. |
| Text | Invalid format buffer. DB/FNR/Subcode .../.../.... |
| Expl. | The format buffer was invalid for use with an update command
(A1/A4) or an add command (N1/N2), for one of the following reasons. - The format buffer specification was invalid (conditional format buffers are not allowed for update operations). - The L9 command"s format buffer format is not allowed for other commands. - The L9 command specified a conditional format in the format buffer. - A floating-point field was addressed using a length other than 4 or 8; or a fixed-point field was addressed using a length other than 4. |
| Actn. | Check program and correct error. |
| Text | Format buffer requires more than 64 KB. DB/FNR .../.... |
| Expl. | The format buffer requires more than 64 KB. |
| Actn. | Contact your database administrator. |
| Text | Maximum value for Adabas NQCID exceeded. DB/FNR .../.... |
| Expl. | The maximum value for the Adabas parameter NQCID was exceeded. |
| Actn. | Contact your Adabas administrator. |
| Text | Maximum value for Adabas parameter NISNHQ was exceeded. |
| Actn. | Contact your database administrator. |
| Text | Error during Open processing. DB/Subcode .../.... |
| Expl. | An error occurred during Open command processing. The detailed reason is given by the subcode which appears in the Additions 2 field of the Adabas control block. For explanations of the subcodes, and appropriate action, please see the documentation for nucleus response codes. |
| Actn. | See the documentation for nucleus response codes, or contact your database administrator. |
| Text | Compressed record too long. DB/FNR/Subcode .../.../.... |
| Expl. | The compressed record was too long. It exceeds the maximum permitted record length for the file. The following subcodes may be indicated. 1 Multiple-value (MU) field. 2 Periodic (PE) group field. 3 MU field. 4 PE group. 5 PE group level. 6 Remaining fields. 7 Record too long for protection logging (internal error). 10 Long alpha or wide field. |
| Actn. | Contact your database administrator. |
| Text | A syntax error in the record buffer was detected. DB .... |
| Expl. | A syntax error in the record buffer was detected during
processing of an OP command. |
| Actn. | Correct the record buffer by changing the OPRB parameter. |
