Nucleus Response Codes

The command was executed successfully.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Depending on the subcode in the rightmost two bytes of the ACB's Additions 2 field or the ACBX's Error Subcode (ACBXERRC) field, one of the following has occurred:

Note:
When one of the subcodes 2-4 is present, the cause could be an Sx command using security-by-value that found at least one ISN.

Open Systems

An ISN list could not be sorted as a result of an excessive number of resulting ISNs, or because during a non-descriptor search a value larger than the corresponding field length in the FDT was found, or because the ISN quantity returned does not correspond with the actual number of records found.

For an S9 command, this response indicates that there is no space available for additional temporary working space. For an S2 command, this response is only a warning and the S2 becomes an S1.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Increase the ADARUN LS parameter value.

Open Systems

Provide sufficient disk space for temporary working space or adapt the FDT to the real field length.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

This response code can only occur with a BT or ET command. The BT or ET command executes successfully. One of the following has occurred, depending on the subcode:

Open Systems

The required function has not been executed completely. For an OP command with command option 2 = E or for an RE command, the specified record buffer length was shorter than the length of the ET data read. The record buffer has been truncated.

For an A1//N1/N2 command, a descriptor value with the TR option is larger than 1144 bytes. In this case, only the first 1144 bytes are stored in the index. Search operations for truncated values may be inexact since only the first 1144 bytes are evaluated. The first 2 bytes of the Additions 2 field contain the number of descriptor values truncated, the third and fourth bytes contain the field name of the descriptor value that is truncated.

For an S1/S2/S4/S9 command, the resulting ISN list may not represent the exact result: this is because the search values and the values in the database were truncated after 1144 bytes during the search operation of an S1/S2/S4 command and during the sort operation of an S2/S9 command.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Open Systems

For an OP or RE command, increase the record buffer length or ignore the warning.

For an S1/S2/S4/S9 command, either perform a post-selection using the complete field values, perform your own sort operation using the complete field values, or ignore the warning.

One of the following has occurred:

• An end-of-file or end-of-list condition was detected.

• A program tried to read/change a multiclient file's record using either a blank or incorrect-length owner ID, or an owner ID that is not allowed for the record.

• Subcode 4: End of LOB value reached. An attempt was made to read a LOB value segment that begins after the end of the value. This response code/subcode is given to an L1/L4 command with Command Option 2 set to L if the ISN Lower Limit value is greater than or equal to the length of the LOB value being read.

The internal Adabas TRS storage directory is full.

Free some of the active queries.

A complex search command was rejected because it was estimated that it would exceed the maximum search time TLSCMD.

The current user's command was interrupted to prevent a Work overflow because of a pending backout operation.

The value specified for the LP parameter might have to be increased.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

A subcode indicating the specific cause and action for this response code appears in the low-order (rightmost) two bytes of the ACB's Additions 2 field or in the ACBX's Error Subcode (ACBXERRC) field. The following are the subcodes and their meanings:

Open Systems

This response is caused by one of the following:

• The last user transaction has been backed out by Adabas (ET logic users only) or an exclusive control user (non-ET user) or an access-only user exceeded the Non-Activity Time Limit;

• The user session was abnormally terminated by the operator and the user issued a command;

• The protection log area (= WORK container) was too small and an internal BT was executed.

The Additions 2 field in the control block contains additional information:

                                           First      Third+
                                            two       fourth
                                           bytes      bytes
                                          -------    -------
                  Transaction timeout :      0          TT
                  Non-activity timeout:      1          TN
                  STOP user           :      2          ST
                  WORK overflow       :      3          LP
                  Security            :      5          SE
                  Deadlock            :      6          DL
                  Open transaction    :      8          OP
                  Open required       :      9          OR

The information in the first two bytes is represented as an integer, and the third and fourth bytes are alphanumeric.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

User actions are described in the subcode list in the explanation.

Open Systems

Check the appropriate reason. If the Adabas nucleus was started without the option OPEN_REQUIRED, and the reason for response 9 was a non-activity timeout or a STOP user, users who started their sessions with an OP command must re-issue their OP command under the following circumstances:

• if they set a User ID

• if they specified restricted file lists

• if they had user-specific timeout values

• if they were not ET users.

If too many transactions are backed out because of a Work overflow, the size of the Work container should be increased.

Too many occurrences for a periodic group.

An error occurred in an MC call during subcommand processing. The error code and additional information can be found in the control block of the subcommand. The first 2 bytes of the Additions 2 field contain the number of the subcommand in binary format. The third and fourth bytes of the Additions 2 field contain the offset of the subcommand's control block in the MC call's record buffer in binary format. All subcommands before the one that failed were executed.

Correct the failed subcommand if necessary and re-issue the subcommands beginning with the one that had failed.

A subcode indicating the specific cause and action for this response code appears in the low-order (rightmost) two bytes of the ACB's Additions 2 field or in the ACBX's Error Subcode (ACBXERRC) field. The following are the subcodes and their meanings:

Invalid file number usage. The file number was modified between successive L2/L5 calls or between successive Lx and Sx calls.

Correct the file number.

An attempt was made to update a file which is either already open for read access or can only be opened for read access. The leftmost two bytes of ACB's Additions 2 field or the ACBX's File Number (ACBXFNR) field may contain the file number.

Do not attempt to update a file with read-only access.

One of the following invalid values was used for a command ID value:

• Binary zeros

• Blanks

• The high-order byte contains the hexadecimal value "FF", but there is no automatic command ID generation

• The three high-order bytes contain the ASCII string "SYN".

Correct the command ID and avoid using any of these invalid command ID values.

An invalid command ID value was detected. One of the following explanations or subcodes is provided:

Correct the command ID.

The command or command option is invalid. A subcode indicating the specific cause and action for this response code appears in the low-order (rightmost) two bytes of the ACB's Additions 2 field or in the ACBX's Error Subcode (ACBXERRC) field.

When using the LNCSTUB module on mainframe systems, 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.

The following are the subcodes and their meanings:

Correct the command code or command option or the previous OP command, and rerun the program.

An invalid starting ISN was specified for an L2/L5 command sequence:

• The ISN was not assigned to a record in the file; or

• The ISN was greater than the MAXISN in effect for the file.

Correct the ISN.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

For an S9 command:

• The ISN list in the ISN buffer was already sorted; or

• The ISN list in the ISN buffer contained an invalid ISN; or

• The "D" option was specified when trying to sort an ISN list by ISN.

Open Systems

An ISN is equal to "0" or is greater than or equal to the first free ISN found in the ISN buffer. The Additions 2 field contains the value of the invalid ISN in 4 byte binary format.

Correct the ISN buffer.

The ISN specified in ISN lower limit field for an S1/S4 or S2/S9 command was not found.

Correct the ISN lower limit.

An invalid ISN buffer length for an S9 command was detected. The number of ISNs to be sorted as provided in ISN quantity is equal to "0".

Depending on the subcode in the rightmost two bytes of the ACB's Additions 2 field or the ACBX's Error Subcode (ACBXERRC) field, one of the following has occurred:

Correct the ISN buffer length.

Sufficient work space was not available to accommodate the combined sizes of the search and value buffers as indicated in the search buffer length and value buffer length fields.

The first two bytes of the Additions 1 field contained an invalid descriptor for an L3/L6/L9 or S2/S9 command.

Depending on the subcode in the rightmost two bytes of the ACB's Additions 2 field or the ACBX's Error Subcode (ACBXERRC) field, one of the following has occurred:

Correct the Additions 1 field.

In an L3 or L6 command, a value repositioning was attempted (bytes 3-8 of the Additions 1 field contain spaces) and the Command Option 2 field did not contain the value "A", "D", or "V". The command ID is released.

Correct the Additions 1 or Command Option 2 field.

An invalid command option has been detected.

Either remove the invalid command option or replace it with a valid option.

The user/DBA attempted to perform a function for a noncluster Adabas nucleus that is available only for an Adabas cluster database.

Either perform the function against a cluster database or change the function.

A syntax error was detected in the format buffer.

Mainframe Systems

On mainframe systems, one of the following subcodes may be used:

On mainframe systems, the following information is returned in the Additions 2 field of the control block:

• The leftmost two bytes contain the two characters being inspected when the error was detected.

• The rightmost two bytes contain the subcode.

Open Systems

One of the following format buffer errors occurred.

• The terminating period was missing;

• The first position contains a period, this only applies to N1 or N2 commands;

• Length and/or format specified with a range definition;

• An invalid element was detected;

• A field segment notation was not correct: it must be specified either as (byte-number,length) or as (byte-number,length,length-2), where byte-number must be either "*" or a decimal number, and length and length-2 are decimal numbers. These numbers must be less than 2,147,483,648;

• A field segment notation was specified for a range of MU fields or for a range of fields within a periodic group.

On open systems, the following information is returned in the Additions 2 field of the control block:

• The leftmost two bytes contain the number of the byte (in binary format) relative to the beginning of the format buffer where the error was detected.

• The rightmost two bytes contain the name of the field being processed when the error was detected.

Correct the format buffer.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

One or more specification errors exist in the format buffer. On mainframe systems, the following information is returned in the Additions 2 field of the control block:

• The leftmost two bytes contain the field name for which the error was detected.

• The rightmost two bytes contain the subcode.

The following specification errors may have been made:

Note:
A collation descriptor (COLDE) can only be specified in the format buffer of the L9 command and only when the decode option has been specified in the user exit. The value returned is not the index value but the original field value.

Open Systems

An error was detected in the format buffer:

• The field name specified is reserved for edit mask usage;

• An index was equal to 0;

• A length specified or taken from the FDT standard length is greater than the maximum length of the required format;

• nnnX was specified with nnn greater than 253;

• A literal with more than 253 characters was specified;

• A subdescriptor, superdescriptor, phonetic descriptor, hyperdescriptor or a collation descriptor was specified;

• A field specified was not present in the file;

• A periodic group name appears without an index;

• A length and/or format was used with a group notation;

• A field in a periodic group was specified without an index;

• A range notation with a group name or a multiple-value field as the first or last element was specified;

• A reference was made to the count of a multiple-value field contained in a periodic group, and no index was included to indicate the periodic group occurrence for which the count was to be returned;

• A collation descriptor with the option HE was specified for an L9 command.

• A count specification was made for a field which was neither a multiple-value field nor was contained within a periodic group;

• A count for a non-multiple value field within a periodic group was specified;

• A length and/or format specification was used with a periodic group notation;

• A (regular or periodic) group containing a multiple-value field was specified;

• Invalid index usage;

• A descending index range was specified;

• A double index was used for a non-periodic field;

• A multiple-value field with an index specification and a multiple-value field without an index specification were used;

• A value cannot be converted to the required format (READ command) or converted to the FDT standard format (UPDATE command);

• The S element was applied to a field that does not have the NC option;

• A field with the NC option was used more than once together with its S element;

• The add option is not compatible with the format/length;

• The specification of a charater set was invalid;

• A field was specified with an edit mask not allowed for the field;

• A field segment notation (byte-number,length) or (byte-number,length,length-2) was not correct. Values for byte-number + length must be less than or equal to the maximum value length + 1, and length-2 must be equal to length. The maximum value for LB fields is 2,147,483,643, for LA fields 16381, an for other values 253 bytes;

• Segment notation is only allowed for values with the format "A".

The following information is returned in the Additions 2 field of the control block:

• The leftmost two bytes contain the number of the byte (in binary format) relative to the beginning of the format buffer where the error was detected.

• The rightmost two bytes contain the name of the field being processed when the error was detected.

Correct the specification error and reissue the command or job. For more information about syntax rules for multiple field and periodic group indexing, refer to the Adabas Command Reference documentation.

A space problem occurred. The following are the subcodes and their meanings:

In an L9 command, the descriptor specified in the format buffer did not agree with the descriptor specified in the search buffer.

Correct the format buffer or the search buffer.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

One of the following format buffer errors occurred (subcodes are shown in the leftmost column):

Open Systems

One of the following situations occurred:

• The format buffer is invalid for use with an update command (A1), add command (N1/N2):

  • Format buffer contains overlapping fields, e.g., GL1-3, GL2-4.;

  • Format buffer contains an 1-N element, e.g., GL1-N.;

  • There is not a 1:1 relation between an L element and the subsequent corresponding element with '*' length;

• A read command uses a format buffer from the format pool, which was previously used by update or add command, and which contains an invalid conversion.

Correct the format buffer or use a different read or update command.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

The internal format buffer space has been exceeded. Either the LWP parameter setting is too small or the internal format buffer requires more than 2 G.

Open Systems

Multiple field or periodic group overflowed when using the N suffix in the format buffer for update.

The following information is returned in the Additions 2 field of the control block:

• The first two bytes will contain the number of the byte (in binary format) relative to the beginning of the record where the error was detected;

• The third and fourth bytes will contain the name of the field being processed when the error was detected.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Increase the size of the LWP parameter and try again. If the problem persists, contact your Software AG technical support representative for assistance.

Open Systems

Because the multiple field or periodic group reached its absolute limit, the application must be re-designed.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

The maximum value for the NQCID parameter was exceeded (the number of TBI and/or TBQ elements is greater than NQCID).

Open Systems

Mismatch of format buffer usage for the supplied command ID.

• A command ID of global ID format buffer has been found in the format pool and has a different file number to the file supplied by the caller;

• The file number was changed in subsequent Adabas calls with the same normal or global command ID.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Adjust the size of the NQCID parameter and try again.

Open Systems

Check the command IDs used in the call and try again.

The maximum value for the NISNHQ parameter was exceeded. This value is 1/4 the ADARUN NH parameter value up to 65535.

Increase the value of the NISNHQ parameter by modifying its ADARUN parameter value in the nucleus startup file, or (on open systems) using ADAOPR.

An error occurred during the processing of a command such as OP or N1. Refer to the hexadecimal subcode that appears in the low-order (rightmost) two bytes of the ACB's Additions 2 field or in the ACBX's Error Subcode (ACBXERRC) field.

On open systems, the corresponding file number is returned in the first two bytes of the Additions 2 field in binary format except for value 8 in the third and fourth byte. The value 0 means the whole database.

The following user actions are possible:

• Wait for the other user or utility to finish, then retry the command.

• Make the file available for all users (on open systems, if value 16 occurred in bytes 3 and 4).

• Restore or unlock the file (on open systems, if value 17 occurred in bytes 3 and 4).

• Rebuild the file's index (on open systems, if value 18 occurred in bytes 3 and 4).

• On open systems, if the value in bytes 3 and 4 of the Additions 2 field is 8, and the nucleus was started with the OPEN_REQUIRED option, you can reissue the OP command immediately. This will cause the other user with the same user ID to be stopped, unless that user is currently active.

• On open systems, if a utility receives a response 48 because non-utility users are still active, you can lock the file with ADAOPR LOCK. This ADAOPR command stops all non-utility users from accessing the file and allows only utility users to access the file until it is unlocked again.

  On mainframe systems, if a utility receives a response 48 because non-utility users are still active, you can lock the file with ADADBS MODFCB FILEREADONLY. The FILEREADONLY command stops all non-utility users from accessing the file and allows only utility users to access the file until it is unlocked again.

The compressed record was too long. It exceeds the maximum permitted compressed record length for the file.

On open systems, the first two bytes of the Additions 2 field contain the length of the compressed record in binary format.

On mainframe systems, the following subcodes may be indicated:

Note:
This response code always means that the compressed record is too long and there are duplicate meanings for subcodes but the subcode can help your Software AG technical support representative analyze where in the code we are giving the response. This can be useful for debugging purposes. Please always provide the subcode when communicating about this response code with your Software AG technical support representative.

On open systems, add a new DATA extent with sufficient block size (block size >= compressed record size + 8). Alternatively you can start the nucleus with OPTIONS=AUTO_EXPAND; then the Adabas nucleus automatically creates a new DATA extent with sufficient block size.

A syntax error in the record buffer was detected during processing of an OP command, an invalid character set was specified, or an invalid time zone was specified.

On open systems, the first two bytes of the Additions 2 field contain the number of bytes (in binary format) relative to the beginning of the record buffer where the error was detected. If a time zone problem occurs, the two right-most bytes of the Additions 2 field in the ACB will contain a subcode; in an ACBX, the Error Subcode field will contain the subcode.

Correct the record buffer and try again.

An error in the record buffer was detected during processing of an OP command.

One of the keywords EXU, UPD, ACC or WCHARSET is duplicated.

On open systems, the following information is returned in the Additions 2 field of the control block:

• the first two bytes contain the number of bytes (in binary format) relative to the beginning of the record buffer where the error was detected;

• the third and fourth bytes contain the open mode that failed (ACC =1, UPD = 2, EXU = 4, WCHARSET = 128)

Correct the record buffer and try again.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

One of the following errors occurred while processing the record, value, or search buffer. In an ACB, the rightmost two bytes of the Additions 2 field contain the subcode; for subcodes 1-5, the leftmost two bytes contain the Adabas name of the field where the error occurred. In an ACBX, the subcode is stored in the Error Subcode (ACBXERRC) field; for subcodes 1-5, the Adabas field name where the error occurred is stored in the Error Character Field (ACBXERRB).

Open Systems

• The value of a G format field was not in floating point format;

• The value of a P format field was not in packed decimal format;

• The value of a U format field was not in unpacked decimal format;

• A variable-length field was specified without a length parameter;

• The SQL null value indicator (S element) has a value of less than -1;

• A field with the NN option is forced to take the SQL null value;

• The resulting value exceeds 4 bytes (longword) if the format is F, or exceeds the maximum (format dependant) length;

• No record with the specified ADAM key was found.

The following information is returned in the Additions 2 field of the control block:

• The first two bytes contain the number of the byte (in binary format) relative to the beginning of the record/value buffer where the error was detected. This value is -1 if a field with the NN option is forced to take the SQL null value.;

• The third and fourth bytes contain the name of the field being processed when the error was detected.

Correct the format, record, value, or search buffer and try again.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

One of the following errors occurred:

Open Systems

The record buffer was too small, or the ISN buffer was too small for a requested multifetch command. The following information is returned in the Additions 2 field of the control block:

• The first two bytes contain the expected buffer size in binary format. This value is -1 if the command would have exceeded the maximum record size.

• The third and fourth bytes contain the name of the buffer that was too small. ("RB" or "IB"). If the error occurred while using a hyperexit, the name of the hyperexit is stored here.

Increase the record buffer or ISN buffer size, as appropriate.

The record buffer for a C3, C5, or ET command is too long. The maximum allowed size is 2048 bytes. The following subcodes provide more information:

Correct the record buffer specification, then reissue the C3, C5, or ET command.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

One of the following occurred:

• During a read-type operation, a field defined with the SQL null (NC) option contained a null value, but the format buffer held no "S" (significant null) indicator for the field.

  In an ACB, the Additions 2 may contain the field name in the leftmost two bytes; the rightmost two bytes may contain the offset into the record buffer. In an ACBX, the Error Character Field (ACBXERRB) may contain the field name; the Error Offset in Buffer (ACBXERRA or ACBXERRG) fields may contain the offset into the record buffer.

• Attempted format conversion was not possible due to incompatible data formats or other compatibility problems.

  In an ACB, the Additions 2 will contain the field name in the leftmost two bytes; the rightmost two bytes will contain the offset into the record buffer. In an ACBX, the Error Character Field (ACBXERRB) will contain the field name; the Error Subcode (ACBXERRC) field will contain the subcode.

  Subcode	Meaning
  0	Conversion error on record decompression.
  1	Invalid conversion between formats.
  2	Invalid length for fixed encoding. For example, user encoding Unicode with code-point size of 2 bytes and no even length specified.
  4	Conversion error of a floating-point field (underflow) when converting to/from a non-IBM floating-point format.
  5	Format conversion of field with NV option is not allowed.
  6	An invalid length was specified ( for example, a wide character field in Unicode encoding must have an even length).
  7	Invalid conversion between formats (different case than subcode 1).
  8	Conversion error of a floating-point field (overflow) when converting to/from a non-IBM floating-point format.
  9	A one-byte field was provided in the record buffer for the occurrence count of an MU field or PE group in a file with extended MU/PE limits. A two-byte occurrence count value is expected.
  20	Unsupported date-time conversion -- internal error.
  21	Date-time value outside valid range. The valid range depends on the date-time edit masks being used in the format or search buffer and the FDT.
  22	Invalid local time – (non-existing local time in the gap that occurs when switching from standard to daylight saving time or when the time zone advances GMT offset)
  23	Year outside range of 1-9999.
  24	Month outside range of 1-12.
  25	Day outside range of 1-n.
  26	Hours outside range of 0-24.
  27	Minutes outside range of 0-59.
  28	Seconds outside range of 0-59.
  30	Accessing a field defined with option TZ but no time zone was specified in the user session. Issue the OP command with TZ='timezone' parameter in the record buffer to set the time zone for the user session.
  31	Invalid daylight saving offset given (fldD) for date-time and time zone.
  n	Data between user and system data representation could not be converted without error and 2-byte error code from ECS.
  254	Numeric field length in format shorter than the field length in the FDT.
  255	Field length exceeded maximum for variable fields.

  Entire Conversion Service (ECS) error codes are described in Entire Conversion Service (ECS) Errors, elsewhere in the Adabas Messages documentation.

Open Systems

A format, length conversion, or truncation error occurred while processing field values in the record buffer or value buffer.

• The value for an FI field is too long;

• The resulting value exceeds the border of the FI field;

• Truncation error of numeric field;

• Truncation of alphanumeric fields or truncation of numeric fields which are converted to alphanumeric, except when OPTIONS=TRUNCATION is enabled in ADANUC;

• A value defined without LA or L4 option with variable length is larger than 253 bytes. This may happen for Unicode fields after conversion to another encoding.

• The length specified for a Unicode field for a character set with fixed character length is not a multiple of the character length: in particular, the length for UTF-16 based character sets must be a multiple of 2, and the length for UTF-32 based character sets must be a multiple of 4;

• The specified value is not a valid date/time value;

• The field does not contain a valid date/time value. This can happen if the value was stored without a date/time edit mask;

• A date/time field with option TZ was specified in the format or search buffer, but there was no time zone specified in an OP command for the current Adabas user session;

• The attempted format conversion was not possible due to incompatible data formats or other compatibility problems.

The following information is returned in the first two bytes of the Additions 2 field, and in the case of an ACBX, also in the field ACBXERRC:

The field name is returned in the third and fourth byte of the Additions 2 field, and in the case of an ACBX in the field ACBXERRB.

In addition, the following information is returned in the case of an ACBX call:

• The offset in the record or value buffer in ACBXERRA;

• The type of buffer in ACBXERRD (‘R’ for error in record buffer, ‘V’for error in value buffer).

Depending on the reasone, correct the appropriate buffer and try again.

On open systems, if a record structure is indicated, run the ADAVFY FIELD against the corresponding file. If this produces errors, then the file must be unloaded, decompressed, recompressed, and reloaded.

If the time zone specification in the OP command is missing, correct and run the appropriate OP command.

One of the following occurred:

Store a shorter descriptor value or collation value.

On open systems, you also can specify the TR option for the descriptor, which truncates larger descriptor values before they are stored in the index. Note that with the TR option, search results may be inaccurate: this is because values that are identical in the first 1144 bytes are considered to be equal to each other.

In an L9 command, the descriptor specified in the format or search buffer or in the Additions 1 field was invalid or the descriptor was not specified:

• The field name specified may not be the name of a descriptor.

• The descriptor specified may be a phonetic descriptor or a hyperdescriptor, which are not allowed in an L9 command.

• On open systems, the descriptor specified may be a collation descriptor with the option HE.

Correct the descriptor in the format buffer, search buffer, or Additions 1 field and try again.

The format could not be found (as defined within format selection criteria).

Adjust the format specification and try again.

Format conversion of a subfield is not possible. The source field has fixed point (F) or floating point (G) format.

Correct the field for which you are attempting format conversion and try again.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

A syntax error was detected in the format or search buffer. Generally in an ACB, the first two bytes of the Additions 2 field contain the two characters under inspection when the error was detected and the rightmost two bytes of the Additions 2 field in the ACB contain one of the following subcodes. In an ACBX, the Error Character Field (ACBXERRB) contains the two characters under inspection when the error was detected and the Error Subcode (ACBXERRC) field contains one of the following subcodes.

Open Systems

A syntax error was detected in the search buffer.

• The first two bytes will contain the number of the byte (in binary format) relative to the beginning of the search buffer where the error was detected;

• The third and fourth bytes will contain the name of the field being processed when the error was detected.

Correct the format or search buffer and try again.

An error was detected in the search buffer, value buffer, or during an S8 command.

Mainframe Systems

On mainframe systems, one of the following subcodes may also be included with this response code:

Open Systems

On open systems, an error was detected in the search or value buffer, or during an S8 command:

• Invalid command option 2 specified for ISN LIST processing (S8 command);

• Invalid element or element order;

• The specified field was neither a descriptor, subdescriptor, superdescriptor nor a phonetic descriptor;

• Invalid connection of partial criteria and/or different indices used for a descriptor contained within a periodic group;

• Invalid use of a phonetic descriptor;

• Invalid periodic group index;

• Invalid index usage;

• The length of a descriptor value was greater than 253 or greater than the permitted length for the required format;

• Invalid format type;

• Invalid file number specification;

• Invalid usage of the S operator - FROM value greater than TO value;

• Invalid usage of the N operator - BUT NOT value was outside the range of the preceding FROM-TO range;

• Invalid comparator;

• The value in the value buffer cannot be converted into the field's FDT format;

• The specified file name is not an ADAM key while using the V option with an A1 or E1 command;

• Invalid value given in the value buffer while using the V option with the A1 or E1 command;

• Invalid usage of the C option - only allowed for collation descriptors;

• A field was specified with an edit mask that is not allowed for the field.

The following information is returned in the Additions 2 field of the control block (not for the S8 command):

• The first two bytes will contain the number of the byte (in binary format) relative to the beginning of the search buffer where the error was detected;

• If the third byte is zero, the fourth byte contains more information about the error:

  • Fourth byte 1: invalid length.

  Otherwise the third and fourth bytes will contain the name of the field being processed when the error was detected.

Correct the search or value buffer or S8 command and try again.

One of the following has occurred:

• The length of the search or value buffers as specified in the search and value buffer length fields, respectively, was not sufficient to accommodate the search criteria specified.

• The first character in the search buffer was a period (.).

• The search buffer does not contain a period (.).

Correct the search or value buffer and try again.

The command ID value specified in the search buffer was invalid.

On open systems, the value in the first two bytes of the Additions 2 field indicates the reason (2 byte binary format):

Correct the command ID in the search buffer and try again.

This response code is used for communication with Adabas utilities and Adabas Online System (AOS), and was returned because the requested function could not be performed on the Adabas system (including checkpoint and security) files or because an error occurred in an AOS or utility function.

The following subcodes may be returned:

Refer to the ADAREP output report for a list of the system files, or to the subcodes in the job output for more information. For AOS, a subcode is displayed in the error message, following the AOS module number. For utility functions, the subcodes may be described within the message text.

If you do not understand the action to take for a response code 64 or subcode, note the subcode and the function that caused the response code, and call your Software AG technical support representative for assistance.

An internal error occurred. The nucleus detected a space calculation error.

Contact your Software AG technical support representative for assistance.

An incompatible owner ID was detected during an update operation on a multiclient file. The owner ID may be blank, or too long.

Contact your Software AG technical support representative for assistance.

One of the following errors occurred:

Retain all related information, and contact your Software AG technical support representative for assistance.

A nondescriptor field was used as a search criterion, and the non-descriptor search facility has been set OFF (the default for this facility is ON).

The ADARUN parameter NONDES has been set to reject non-descriptor searches; either reset the NONDES parameter to its default value, or remove non-descriptor searches from your application. Natural provides a trace facility which locates such Natural application characteristics. Contact Software AG for details.

An overflow occurred in the table of sequential commands.

The DBA may increase the value used for the LQ parameter or RC commands may be used.

An overflow occurred in the table of resulting ISN lists.

The DBA may increase the value used for the LI parameter or RC commands may be used.

One of the following errors occurred:

The DBA may increase the value used for the NU parameter.

An overflow occurred in the section of the Work data set (mainframe systems) or the temporary working space (open systems) in which resulting ISN lists are stored.

On open systems, please note that for read-only databases, temporary working space is only created if a location for it is explicitly specified (environment variable TEMPLOCn or entries for TEMPORARY_LOCATION in the file DBnnn.INI); otherwise only some of the space in the Adabas buffer pool is used for storing the ISN lists.

On mainframe systems, the DBA may increase the size of the Work data set and/or the number of saved ISN lists during an Adabas session may be decreased.

On open systems, provide enough temporary working space. For read-only databases, specify the location for the temporary working space explicitly or increase the size of the Adabas buffer pool (ADANUC parameter LBP).

Note:
The processing of ISN lists was changed for Adabas Version 5.1. If you get this error with an Adabas Version 3 database, please refer to the Adabas Version 3 documentation.

No space was available on the Work data set for complex find commands.

On open systems, increase the size of the Work data set.

On mainframe systems, increasing the size of the Work data set alone will not solve this problem. Instead, set the value of LWKP2 (WORK-PART-2) to a higher value than the calculated one (whatever that might be). Then increase the size of the Work data set to ensure there is sufficient space for WORK-PART-3.

Attempts to allocate additional Associator or Data Storage extents for a file were issued, but the maximum number of extents that can be handled by the FCB have already been allocated.

On mainframe systems, BT (backout) or autorestart processing could cause the file to be locked because of inadequate extent space (see response code 48).

On open systems, the last extent is allocated only for a command which is being backed out and for AUTORESTART and ADAREC REGENERATE. The first two bytes of the Additions 2 field contain the highest possible extent number (in binary format). The third and fourth bytes indicate where the overflow occurred. Possible values are: "DS" (Data Storage), "AC" (Address Converter), "NI" (Normal Index) and "UI" (Upper Index).

On mainframe systems, ask your DBA for assistance; Associator or Data Storage extents may have to be reallocated.

On open systems, unload the file and reload it with appropriate initial allocations.

An overflow occurred in an inverted list index (the maximum is 15 levels).

Unload and reload the file with an appropriate padding factor for the Associator.

Sufficient space was not available for a required Associator or Data Storage extent.

On mainframe systems, the following subcodes further define the error:

On open systems, the third and fourth bytes of the Additions 2 field contain either "AS" (Associator) or "DS" (Data Storage). You can also get the response 77 if you specified an explicit RABN for an Associator or Data Storage extent and the requested space is not available at the requested RABN. Please note that Adabas distinguishes between small (< 16KB) and large (>= 16KB) index blocks. This means that a response 77 can be returned even though there are enough free Associator blocks, but the free Associator blocks have the wrong size.

On mainframe systems, ask your DBA for assistance; Associator or Data Storage extents may have to be reallocated.

On open systems, add a new Associator or Data Storage extent to the database using the ADADBM utility or specify a RABN where the requested space is available.

Note:
Response 77 can sometimes be prevented by enabling database autoexpand to execute in the online mode (specify the open systems nucleus parameter OPTIONS=AUTO_EXPAND).

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

The cause of this response is indicated by one of the following subcodes:

Open Systems

An overflow occurred in the free space table (FST) as a result of Associator or Data Storage fragmentation, or the maximum number of DSST extents has already been allocated.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

If the file has reached the 16-MB limit, you might convert it to a file with the 4-byte ISN option or to an expanded file.

Open Systems

If it is an FST problem, reorder the database. If it is a DSST problem, which can only occur in the context of a utility, refer to the message DSSTALL for further information.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

A collation descriptor exit or hyperexit error occurred. The following table describes the possible subcodes for this response code and their meanings:

Open Systems

A hyperexit is not available to the nucleus. The following information is returned in the Additions 2 field of the control block:

• The first two bytes contain the number of the hyperexit,;

• The third and fourth bytes contain the name of the hyperdescriptor.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

The following table describes the actions you should take for each possible subcode for this response code:

Open Systems

Define the hyperexit and restart the nucleus.

An MU or PE field error occurred, as described by the subcode:

Correct the MU or PE field problem and try again. If the problem persists, contact your Software AG technical support representative for assistance.

A hyperexit routine returned an invalid ISN.

Correct the hyperexit routine logic and restart the nucleus.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

A hypertable overflow occurred.

Open Systems

A hyperexit routine returned an invalid ISN.

The following information will be returned in the Additions 2 field of the control block:

• The first two bytes contain the offset the invalid ISN in the specified ISN buffer in binary format;

• The third and fourth bytes contain the name of the hyperdescriptor.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Open Systems

Correct the hyperexit routine and restart the nucleus.

Too many values were present for a subdescriptor or a superdescriptor.

Reduce the number of subdescriptor or superdescriptor values and try again.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Too many descriptor values were present for an update or add record command.

Open Systems

The descriptor value table space cannot be allocated from the buffer pool.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Open Systems

Increase the size of the LBP parameter.

A hyperdescriptor exit return error occurred for one of the following reasons:

• An incorrect sign for a packed descriptor value was created.

• A value with an incorrect length byte was returned.

• The ISN was changed by an update command.

On open systems, the following information is returned in the Additions 2 field of the control block:

• The first two bytes contain a value. This value can be:

  1	the hyperdescriptor pool exceeds the nucleus buffer pool
  2	the hyperexit has returned an invalid pointer, length or count value
  3	an element in the user-defined format buffer is not a parent field of the hyperdescriptor
  4 - 255	Adabas response code
  >255	user-defined error return for hyperexit routine

• The third and fourth bytes contain the name of the hyperdescriptor or the name of the parent field.

The Adabas buffer pool is locked; it is too small to accommodate all blocks needed for (parallel) command execution.

Check the length of the buffer pool (LBP) as follows:

This response code generally occurs when there is a workpool (LWP) shortage. Sufficient work pool space is not available or the sort work space is too small (even if only one user is active).

On mainframes systems, when this response code occurs, refer to the hexadecimal subcode that appears in the low-order (rightmost) two bytes of the ACB's Additions 2 field or in the ACBX's Error Subcode (ACBXERRC) field. This subcode describes what kind of operation encountered the error.

The following table describes the mainframe subcodes and provides recommended actions.

For mainframe systems, review the actions described in the table above.

For open systems, verify the parameter values for the database that relate to the working storage allocation. Ask your DBA to increase the size of the LWP or LS parameter, as necessary.

The UQE was already in use, and an attempt was made to execute two commands at the same time for the same user.

An I/O error occurred on DDWORKR4.

An I/O error occurred on the Work LP area.

An error occurred during ADARES REPAIR utility execution.

An I/O error occurred during buffer flush. Additions 2 may contain RABN.

A uniqueness violation of a unique descriptor was detected during a store or update processing if subtransactions are not activated, or otherwise at end of a subtransaction. The third and fourth bytes of the Additions 2 field contain the name of the descriptor which caused the uniqueness conflict.

Check the descriptor values.

An I/O error occurred.

On open systems, the first 2 bytes of the Additions 2 field ( in binary format) contain the extent number. The third and fourth bytes contain the container type ("AS" for ASSO, or "DS" for DATA or "WO" for WORK).

On open systems, check whether any disk devices have gone offline or check the error log for hardware errors.

An error has occurred using one of the client-based Adabas add-on products such as Adabas System Coordinator, Adabas Fastpath, Adabas Vista, Adabas Transaction Manager, or Adabas SAF Security.

• Subcodes 1-20 are generated by Adabas Fastpath.

• Subcodes 21-69, 32766 and 32767 are generated by Adabas System Coordinator.

Please refer to the documentation for the appropriate add-on product for further information on subcodes and console messages that can help you resolve the error.

Space calculation error.

Retry the open operation.

The prefetch table record buffer specified in the UDB is too small.

Either a GETMAIN error occurred or there was insufficient space when performing prefetch. Prefetch is switched off.

The specified command ID is already active on another database for this user.

The command ID pool is full.

Increase the size of either or both the ADARUN NQCID or NU parameters.

The specified ISN was invalid for one of the following reasons:

• An HI command was issued with ISN less than MINISN or with an ISN equal to zero (0).

• An N2 command was issued with ISN equal to 0 or larger than the MAXISN in effect for the file.

• An N2 command was issued and the specified ISN was assigned to another record in the file.

• An A1, L1/L4, E1, or S1/S2/S4 (with FB) command was issued for a nonexistent ISN.

• An L3/L6 command found an ISN in the index which did not exist in the address converter.

• An N1/N2 command tried to access a file protected by security-by-value, but the command user is not authorized to access the file.

• A read or update command tried to access a multiclient file's record using either a blank or incorrect-length owner ID, or an owner ID that does not apply to the record.

• An RI command was issued for a record that has been updated earlier in the same transaction. The record cannot be released from hold status prior to transaction end. On mainframe systems, subcode 5 is issued for this reason.

• Subcode 19 is given when a base file record is not found in the address converter (AC). At the end of a LOB update in the LOBfile, the associated base file record no longer existed.

• Subcode 249 is given only when Adabas Vista is in use. Refer to the Adabas Vista documentation for more information.

Correct the ISN problem and try again.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

A refresh file error occurred. One of the following subcodes may be present:

Open Systems

A refresh file function using the E1 command was issued (E1 with ISN=0), and one of the following situations has occurred:

• PGM_REFRESH is not specified for the file.

• The user session is not at ET status.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Open Systems

If you forgot to specify the ISN for the E1 command, or the command was not issued at ET status, correct your program. If PGM_REFRESH was not specified for the file in question, specify PGM_REFRESH for the file with ADADBM.

An error was reported by the Adabas cluster messaging service on the sender's side. The message was not sent. One of the following subcodes may be present:

If you are unable to resolve the problem, contact your Software AG technical support representative.

An error was reported by the Adabas cluster messaging service on the receiver's side. The message was sent. One of the subcodes described for response code 123 may be present.

If you are unable to resolve the problem, contact your Software AG technical support representative.

An internal error occurred when one cluster nucleus attempted to issue an internucleus command to one or more of the other cluster nuclei. This condition usually leads to abnormal termination.

Contact your Software AG technical support representative.

A messaging error occurred during internucleus communication:

• The nucleus did not respond within the allotted time (see the ADARUN MXMSG parameter); or

• One or more problems occurred in what could be a broadcast; that is, a communication with multiple targets. In this case, each individual ACB contains either response code 0 or 123 or 124.

If you are unable to resolve the problem, contact your Software AG technical support representative.

In an Adabas cluster environment, the user attempted to perform an Adabas function that is not yet supported by Adabas cluster nuclei.

An error identified by one of the following subcodes occurred in an Adabas sysplex cluster environment:

For subcode 1, correct the application program attempting to issue commands using the NUCID. If that is not the case, or for other subcodes, contact your Software AG technical support representative for assistance.

In most cases this response code will be given to the user in the URBRRSP field of the URBR block with the subcode in the URBRSUB field. The subcode appears either in the low-order (rightmost) two bytes of the additions 2 field or in the URBRSUB field. It indicates the specific cause and action for this response code. The following are the subcodes and their meanings:

The exact meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

This response code indicates that an error occurred while Adabas was reading or updating a LOB file. The subcode indicates the kind of error.

If the subcode is less than 256, it is the same as the original response code that occurred during LOB file processing. The most likely subcodes are listed in the table below. For subcodes not listed, see the description of the Adabas response code with the same value.

If the subcode is greater than 256, it signals an error condition unique to the processing of LOB files. These subcodes are listed in the table below.

Open Systems

LOB data processing may fail because of concurrent updates. If a new attempt to process the LOB data also fails, this response code is returned.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Resolve the problem described in the subcode list in the explanation.

Open Systems

If this response code is reproducible even though the accessed LOB fields are not being updated, contact your Software AG technical support representative.

If this response code is returned with subcode 297, a planned feature for large object (LB) fields (for example, character code conversion of LB field values) is not yet supported.

An error was detected when an attempt was made to replicate a compressed record. The subcode identifies the kind of error.

An error was detected when creating system fields. The subcode identifies the kind of error.

A requested lock could not be granted because a deadlock situation has been detected.

If the operation already performed in the current transaction have produced a new, useful and consistent database state, you should perform an end of transaction. Otherwise you should backout the transaction.

One of the following occurred:

• The ISN specified with an update (A1) command was not in hold status for the user and command option H was not specified.

• An ET or BT command specifying the M (multifetch) option specified an ISN in the ISN buffer that is not in hold status for the user. All currently held ISNs are released from hold status.

  In this case on open systems, the first 2 bytes of the Additions 2 field (in binary format) contain the offset of that ISN in the ISN buffer.

Put the ISN in hold status before using the A1 command or the multifetch ET or BT commands.

If Adabas Transaction Manager is in use, verify that the setting for the Transaction Model parameter is appropriate for the program that was executing and is also appropriate for the runtime environment in use.

The exact meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

On mainframe systems, one of the following situations occurred:

• An N1/N2 command was issued, but no hold queue entry was available.

• A command was issued with the return option specified that attempted to hold an ISN already in the hold queue for another user. The command is not placed in wait status.

Use the subcode associated with this response code to further clarify why this response occurred.

Open Systems

On open systems, one of the following situations occurred:

• An attempt was made to insert a record using an N2 command with an ISN that is in hold status.

• An attempt was made to hold an ISN which was in hold status for another user and the R option is specified. In this case, the Additions 2 field contains the binary value 0;

• Hold queue overflow. In this case, the Additions 2 field contains a value not equal to 0.

  Note:
  This hold queue overflow error can only occur with Adabas versions < 5.1.

The exact meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

An invalid buffer length was detected by the Adabas interface routine. If the command uses a classic ACB, the buffer is larger than 32,767. If the command uses an ACBX, the buffer is greater than 2,147,483,647, or the send length in the ABD is greater than the buffer length. The subcode identifies the buffer type:

Open Systems

An invalid buffer length was detected by the Adabas interface routine, in an MC call, or one of the following errors occurred for a multifetch command:

• the buffer header was invalid (both offsets are set)

• at least one ISN buffer offset was not divisible by 4

• the start offset was outside the multicall buffer range

• the record buffer was not large enough to contain all subcommand control blocks.

The value in the Additions 2 field identifies the buffer: the first 2 bytes contain the buffer number in binary format, the last two bytes contain the buffer name, as shown in the following table:

                  Bytes 1-2        Bytes 3-4
                     1             FB (format buffer)
                     2             RB (record buffer)
                     3             SB (search buffer)
                     4             VB (value buffer)
                     5             IB (ISN buffer)

Correct the buffer length and try again.

The exact meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

The ISN was invalid. The ISN transformation resulted in a negative ISN or an ISN greater than the maximum ISN permitted for the file.

Open Systems

A user buffer is not accessible by the Adabas interface routine.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Open Systems

Check whether the control block, format buffer, value buffer, record buffer and ISN buffer have valid addresses and lengths. Check whether the control block, ISN buffer and record buffer are write-protected.

The Adabas nucleus was either not active or not accessible (a call could not be sent to the Adabas nucleus when the command was issued). In an ACB, refer to the hexadecimal subcode that appears in the low-order (rightmost) two bytes of the Additions 2 field; in an ACBX, refer to the binary subcode that appears in the Error Subcode (ACBXERRC) field.

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (in the ACB) or the ACBXERRC field (in the ACBX) may contain the ID of the Entire Net-Work node that issued this response code.

The following are the decimal equivalents of the subcodes and their meanings:

Review the user actions provided in the explanation above.

A communication error was detected. The Additions 2 field contains the system service completion code which caused the error response.

Check the Additions 2 field.

Too many database nuclei have been used in parallel. The Additions 2 field contains the maximum number of nuclei allowed in parallel.

Do not use more database IDs in a single program than the value given in the Additions 2 field.

A command queue overflow occurred.

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (in the ACB) or the ACBXERRC field (in the ACBX) may contain the ID of the Entire Net-Work node that issued this response code.

The DBA may increase the value of the NC parameter or the command may be issued when there is a lower level of command activity.

The internal user buffer was not large enough to contain the user buffer areas.

The DBA should increase the value of the LU parameter used by the Entire Net-Work nucleus.

A second Adabas call was issued while the first one was still being processed.

Issue only one call at a time.

One of the following occurred:

• The Adabas call was cancelled by the user (open systems).

• The command was rejected because it resulted in a trigger being fired, but the queue is full at this time. (mainframe)

On open systems, no action is required for this informational message. On mainframe systems, retry the command.

A command resulted in a pre-command trigger being fired. The triggered procedure returned a nonzero command, so the command was not executed.

Check the Additions 4 field for the error returned from the procedure.

A command resulted in a post-command trigger being fired. The triggered procedure returned a nonzero command, indicating an unsuccessful execution of the procedure.

Check the Additions 4 field for the error returned from the procedure.

A command resulted in either a pre- or post-command trigger being fired; however, Adabas Triggers has been shut down with the option to reject all commands that result in a trigger being fired.

Determine the cause of the shut-down and resolve the problem. If rejection of commands is not the required action in such a situation, then set the error action field in the Adabas Triggers profile to halt or ignore.

The Adabas link module is missing or invalid. One of the following occurred:

• No Adabas link module is linked to the Natural nucleus and the Adabas link module specified in the Natural profile parameter ADANAME could not be loaded.

• (CICS only) The loaded Adabas link module is macro-level in a command-level only environment.

Check the setting of the Natural profile parameter ADANAME and/or provide the correct version of the Adabas link module in one of the current steplibs.

Too many Associator and Data Storage blocks were marked as active in the buffer pool for a single command.

The RABN chain in the header list of the Adabas buffer pool is invalid.

No additional space is available for the Adabas buffer pool.

Increase the value of the ADARUN LBP parameter.

On open systems, because the buffer pool overflow is normally caused by too many blocks in the buffer pool waiting to be written to disk, specifying a low value for the WRITE_LIMIT parameter is recommended.

The RABN to be linked into the RABN header chain is already in the chain.

Too many work areas were allocated for the command.

A descriptor name was either invalid or did not exist in the descriptor value table (DVT). For expanded files: the descriptor does not exist on all component files.

On open systems, this error may occur during ADAREC generate if one of the following occurs:

• A file was loaded with an incorrect FDT.

• ADAINV was not reexecuted following a stop at a SYNP checkpoint.

In an ACB, the leftmost two bytes of Additions 2 may contain the descriptor name; in an ACBX, the Error Character Field (ACBXERRB) may contain the descriptor name. If this occurred for an expanded file, check to see if there is an FDT mismatch between the components of the file.

On open systems, bytes 3 and 4 of the Additions 2 field contains the name of the descriptor that caused the error.

On open systems, if the error is not a handling error, run the INDEX option of ADAVFY and contact your Software AG technical support representative.

An error was detected in an inverted list index; a descriptor value was not found during a delete operation. The cause may be damage in the Associator.

On open systems, bytes 3 and 4 of the Additions 2 field contains the name of the descriptor that caused the error.

On open systems perform the following steps:

1. Locate the descriptor that caused the error in the Additions 2 field of the user control block;

2. Run the VERIFY option of ADAINV for this descriptor and save the output;

3. Reinvert the descriptor;

4. If necessary, restart the database (if this is possible);

5. Send the following information to your Software AG technical support representative:

   • The output of the VERIFY option of ADAINV;

   • All available PLOGs;

   • The FDT of the file containing the error;

   • If the nucleus crashed, the crash directory.

The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

The field in a coupled file does not exist or the coupled list is invalid.

Open Systems

An error was detected in an inverted list index; a descriptor value was already present during an insert operation.

Bytes 3 and 4 of the Additions 2 field contains the name of the descriptor that caused the error.

The method of resolving the error varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems.

Mainframe Systems

Open Systems

Complete the following steps:

1. Locate the descriptor that caused the error in the Additions 2 field of the user control block;

2. Run the VERIFY option of ADAINV for this descriptor and save the output;

3. Reinvert the descriptor;

4. If necessary, restart the database (if this is possible);

5. Send the following information to your nearest support center:

   • The output of the VERIFY option of ADAINV;

   • All available PLOGs;

   • The FDT of the file containing the error;

   • If the nucleus crashed, the crash directory.

An internal command ID required during coupling processing was not found.

The Adabas RABN required for the command could not be located for one of the following reasons:

• The buffer segment was called with a RABN of zero.

• The specified RABN does not belong to this database and is invalid.

On open systems, the Additions 2 field contains the invalid RABN in 4 byte binary format.

On open systems, run the LOST, INDEX and DATA options of ADAVFY for the file in question and contact your Software AG technical support representative.

The constant set used by Adabas could not be located.

On mainframe systems, an ISN was less than the MINISN or greater than the MAXISN setting in effect for the file.

On open systems, the maximum possible ISN of the file was reached and no more can be allocated.

On open systems, if the file contains significantly less than 2³² records, you should unload the file with ADAULD and reload it with ADAMUP without USERISN. However, you must be aware that problems may arise if the ISNs have semantics for you - if, for example, you use the ISNs to reference records in this file, additional reorganization of these references will be necessary. The alternative to unloading and reloading the data is to split up your data into more than one file, and to adapt your application accordingly.

An invalid Data Storage RABN was detected.

On open systems, the Additions 2 field contains the invalid RABN in 4 byte binary format.

On open systems, run the DATA option of ADAVFY for the file in question and contact your Software AG technical support representative.

For an L2/L5 command with start ISN, the Data Storage RABN stored in the address converter for the file is invalid.

An inconsistency was detected between the index and Data Storage.

This response code can be expected when reading a descriptor value for a ciphered file if an incorrect cipher code was used.

Run the check utilities (especially ADAICK and ADAVAL) against the file, and contact your Software AG technical support representative.

Either an inconsistency was detected in an inverted list or an internal error occurred during inverted list processing.

On open systems, the Additions 2 field contains the inconsistent RABN in 4-byte binary format.

On mainframe systems, the following possible subcodes are associated with this response code:

On mainframe systems, run ADAICK to determine whether an inconsistency exists in an inverted list. If not, contact your local Software AG technical support representative. Make sure to report the subcode to your Software AG technical support representative.

On open systems, check if an autorestart or an ADAREC REGENERATE have disabled the index. If not, run the INDEX option of ADAVFY for the file in question. If the INDEX option signaled errors, you should recreate the entire inverted list with ADAINV REINVERT ALL or contact your Software AG technical support representative.

A record could not be found in the Data Storage block in which it should have been contained as indicated by the address converter. On mainframe systems, if this response code is returned to the ADAULD UNLOAD utility function with the parameter SORTSEQ, the file might be inconsistent and data lost.

Subcode 19 is issued because the base file record was not found in Data Storage. At the end of a LOB update in teh LOB file, the associated base file record was no longer present in the data storage block.

On mainframe systems, check the file with the check utilities, especially ADAACK, and contact your Software AG technical support representative.

On open systems, run the AC option of ADAVFY for the file in question and contact your Software AG technical support representative.

An internal error occurred when updating a multiple-value field:

Internal error; identifier could not be found in Work part 3.

Autobackout was executed and the start of a transaction could not be located.

Necessary ET data was not found in the appropriate Work block.

On open systems, save WORK1 and send it to your nearest Software AG technical support representative together with a description of what caused the pending autorestart and, if possible, the dump directory and the PLOG. Then restore and regenerate the database.

An internally assigned number for a database I/O operation was detected as invalid.

A phonetic field name could not be found.

The ADAM field could not be found in the compressed record.

Referential integrity has been violated. Bytes 3 and 4 of the Additions 2 field contain the name of the violated constraint. Bytes 1 and 2 of the Additions 2 field contain the reason as a two-byte binary number:

Handle the referential intergrity violation, for example, write an error message.

The DEUQ pool is too small.

Increase the ADARUN LDEUQP parameter.

An attempt was made to duplicate a descriptor value for a unique descriptor. In an ACB, the leftmost two bytes of the Additions 2 field may contain the descriptor name; in an ACBX, the Error Character Field (ACBXERRB) may contain the descriptor name. The following subcodes may accompany this response code:

An inconsistency in the inverted list index was found during an update operation. In an ACB, the leftmost two bytes of Additions 2 may contain the descriptor name; in an ACBX, the Error Character Field (ACBXERRB) may contain the descriptor name. This response code can also occur if UTYPE=EXU was specified for an ADARES BACKOUT operation that uses the sequential (SIBA) log.

Either an invalid cipher code or an Adabas SAF Security or Adabas security violation was detected.

From Adabas SAF Security processing, the command could not satisfy the necessary security checks and may be accompanied by a subcode as follows:

For more information about Adabas SAF Security, read the Adabas SAF Security documentation.

Resolve the security error, perhaps by simply supplying the correct password.

The specified password was not found.

Supply the correct password.

An attempt was made to use a file for which the user is not authorized, or the file password is being changed.

Either correct the authorization, or retry the operation with the new password.

An attempt was made to delete a record in a file for which the user is not authorized.

On mainframe systems, a password pool overflow occurred.

On open systems, the password supplied is already in use.

On open systems, change the password to one that is not already existing.

Adabas SAF Security completed phase 1 of logon and requested phase 2. This is an internal Adabas SAF Security and ADALNK two-phase response code for a remote workstation logon. This code is normally not displayed or presented.

For more information, read your Adabas SAF Security documentation.

Send a phase 2 logon request to Adabas SAF Security.

As an Adabas SAF Security remote user, you should execute a phase 1 logon. The logon ID and your password are sent to Adabas SAF Security. This response indicates that two-phase logon can continue.

For more information, read your Adabas SAF Security documentation.

If the user application receives this response, it is on a workstation platform that does not have the proper Adabas link routine installed. This response code is intercepted by the workstation Adabas link routine and phase 1 logon is performed.

Adabas SAF Security detected an expired password on the server.

Create a valid password on the server for ACF2, RACF, or Top Secret. Entire Net-Work users may use the Adabas SAF Security feature.

On mainframe systems, a logical ID was greater than 255 (internal error).

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (in the ACB) or the ACBXERRC field (in the ACBX) may contain the ID of the Entire Net-Work node that issued this response code.

On open systems, a receive buffer was lost in NETRDI.

On open systems, the DBA may increase the value of the NAB or NC parameters in the NETRDI in the target node.

On mainframe systems, an invalid ID table index in the UB (internal error) occurred.

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (in the ACB) or the ACBXERRC field (in the ACBX) may contain the ID of the Entire Net-Work node that issued this response code.

On open systems, a remote utility cannot be executed because OPTIONS = LOCAL_UTILITIES is set for the database.

On open systems, contact the DBA of the remote database.

On mainframe systems, an invalid input/output buffer was encountered for an internal command.

On open systems, a requested function is not implemented in the target architecture.

On open systems, execute the utility on the target node.

ID table not found (SVC not properly installed).

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (in the ACB) or the ACBXERRC field (in the ACBX) may contain the ID of the Entire Net-Work node that issued this response code.

The following table describes the possible subcodes that might occur if an Adabas DBID/SVC routing table error occurs:

Inform the DBA. The Adabas installation procedure was not properly executed.

Internal command issued from Adabas version 4 Adalink.

On mainframe systems, an SVC 04/16 call was received from Adabas version 4 Adalink, with Adabas version 5/6/7 UB or AMODE=31.

On open systems, the Adabas interface (adalnkx, adalnk, adalnknc) used by the application program, or the Entire Net-Work version used is not supported by the Adabas nucleus. For example, the Adabas nucleus Version 6.1 does not support the Adabas interface of Version 5.1. If a 32-bit version and a 64-bit version of Adabas exists for an operating system, the 64-bit nucleus does not support the Adabas interface of the 32-bit version - 32-bit applications must use the 32-bit mode Adabas interface of the 64-bit version.

Note:
The compatible Entire Net-Work versions supported by an Adabas open systems version are documented in the Adabas open systems Release Notes.