Nucleus Response Codes

The command was executed successfully.

Depending on the subcode in the rightmost two bytes of the additions 2 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.

Increase the ADARUN LS parameter value.

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:

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.

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.

A subcode appears in the low-order (rightmost) two bytes of the additions 2 field indicating the specific cause and action for this response code. The following are the subcodes and their meanings:

Too many occurrences for a periodic group.

A subcode appears in the the low-order (rightmost) two bytes of the additions 2 field indicating the specific cause and action for this response code. The following are the subcodes and their meanings:

Invalid file number usage. The file number was modified between successive L2/L5 calls.

An attempt was made to update a file which was opened for access only. The leftmost two bytes of additions 2 may contain the file number.

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

• X'00000000'

• X'40404040'

• X'FFxxxxxx'

Avoid usage of any of the above command ID values.

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

• The command ID value specified with the GET NEXT option of an L1/L4 command was not found.

• The command ID value was not found and the L3/L6 call was not an initial call.

• The command ID value specified for the L3/L6 command was assigned to another L2/L5 or L9 command.

• The command ID value specified for the L9 command was assigned to another L2/L5, L3/L6 or L9 command.

• An invalid global format ID was specified.

• The command ID is already present in the format pool, but for another file.

1: The command ID value was not found in the sequential command table. Either this is not an initial call and there was no previous initial call, or the initial call was issued for another file.

6: The command ID value specified for the S8 command was not found.

7: The command ID value specified was assigned to an internal format buffer for a different file.

8: The command ID value specified for the S8 command is for an unsorted ISN list.

9: An application running with PREFETCH=YES or PREFETCH=OLD attempted to dynamically reverse the read direction of an L3/L6/L9 command. This is not allowed.

The command is invalid. A subcode appears in the low-order (rightmost) two bytes of the additions 2 field indicating the specific cause and action for this response code.

When using the LNCSTUB module, 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:

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.

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.

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

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.

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 or S2/S9 command:

• the additions 1 field contained a descriptor different from that contained in the search buffer; or

• the field was not a descriptor; or

• the descriptor was changed between successive calls; or

• the descriptor is contained within a periodic group.

L3/L6 command; a value repositioning was attempted (bytes 3-4 of the additions 1 field contain spaces) and the command option 2 field did not contain the value "V". The command ID is released.

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.

One of the following syntax errors was detected in the format buffer:

• The terminating period was missing.

• The first position contained 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.

• Format `C.' was specified for an update command.

One or more specification errors exist in the format buffer. If available, then the short name of the field for which the error occurred is stored in the leftmost two bytes of the Additions 2 field.

Any of the following specification errors may have been made:

• A phonetic descriptor or hyperdescriptor was specified;

• Field specification error:

  - the specified field name is reserved for edit masks;

  - the field is not in the selected file.

• Indexing error:

  - no index was specified for a periodic-group name or field;

  - a group or multiple-value field index greater than 191 was specified;

  - the specified index was zero (0);

  - the specified index range is descending;

  - indexes are missing for some of the multiple-value fields specified;

  - a reference to a multiple-value field count is missing an index.

• Periodic-group error:

  - a reference to a periodic group is missing an index;

  - the command specified a group containing a multiple-value field;

  - a periodic-group reference specifies a length/format;

  - no index was specified in a periodic-group reference.

• Group error: a group reference specified a length/format.

• Multiple-value field error:

  - a count was specified for a non-multiple-value field;

  - the methods for indexing multiple-value fields were mixed. Only one type of indexing can be used in the format buffer.

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:

L9 command; the descriptor specified in the format buffer did not agree with the descriptor specified in the search buffer.

One of the following format buffer errors occurred:

The internal format buffer requires more than 64K.

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

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

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 additions 2 field.

The compressed record was too long. It exceeds the maximum permitted compressed record length for the file. The following subcodes may be indicated:

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

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

One of the following errors occurred while processing the record, value, or search buffer (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):

One of the following errors occurred:

The record buffer for a C3, C5, or ET command is too long. The maximum allowed is 2048 bytes. The following subcodes (in hexadecimal) may be indicated:

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

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.

  Additions 2 may contain the field name in the leftmost two bytes; the rightmost two bytes may contain the offset into the record buffer.

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

  Additions 2 contains the field name in the leftmost two bytes; the rightmost two bytes contain the subcode:

  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.
  8	Conversion error of a floating-point field (overflow) when converting to/from a non-IBM floating-point format.
  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.

One of the following occurred:

L9 command; the descriptor specified in the search buffer or in the additions 1 field was invalid, or the descriptor was not specified.

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

Format conversion of a subfield is not possible. The source field has "F" or "G" format.

A syntax error was detected in the format or search buffer. Generally, the first two bytes of the additions 2 field contain the two characters under inspection when the error was detected. The rightmost two bytes of the additions 2 field contain one of the following subcodes, which further defines the error:

An error was detected in the search buffer. One of the following subcodes may also be included with this response code:

One of the following has occurred:

• The length of the search and/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 "."

• The search buffer does not contain a "."

The command ID value specified in the search buffer was not found.

This response code is used for communication with Adabas utilities and Adabas Online System (AOS), and was returned for one of the following reasons:

• The requested function cannot be performed on Adabas system (including checkpoint and security) files. Refer to the ADAREP output report for a list of the system files, or to the subcodes in the job output for more information.

• An error occurred in an AOS or utility function. For AOS, a subcode is displayed in the error message, following the AOS module number. For utility functions, the subcodes are described within the message text.

If you do not understand the action to take for a response code 64 and/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.

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

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 and/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 and/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 dataset in which resulting ISN lists are stored.

The DBA may increase the size of the Work dataset and/or the number of saved ISN lists during an Adabas session may be decreased.

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

Increasing the size of the Work dataset 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 dataset to ensure there is sufficient space for WORK-PART-3.

Attempts to allocate additional logical file extents for a file were issued, but the maximum that can be handled by the FCB have already been allocated. BT or autorestart could cause the file to be locked because of inadequate extent space (see response code 48).

Ask the DBA for assistance; Associator or Data Storage extents may have to be reallocated.

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

Sufficient space was not available for a required Associator or Data Storage extent. The following subcodes further define the error:

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

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.

Either a collation descriptor exit (subcode `CDX'n where "n" is the one-byte binary collation descriptor exit number) or a hyperdescriptor exit ("hyperexit") was not specified in ADARUN.

Reissue ADARUN with the CDXnn or HEXnn parameter. Refer to the Adabas Operations documentation for more information about ADARUN parameters, and to the DBA Tasks for a description of user exits.

A hyperexit routine returned an invalid ISN.

Hypertable overflow.

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

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

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.

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. When this response code occurs, refer to the hexadecimal subcode that appears in the low-order (rightmost) two bytes of the additions 2 field. Following are the subcodes and their meanings.

For all subcodes you can increase the LWP ADARUN parameter value and retry the operation, in addition to any subcode-specific action listed in the table below:

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.

An I/O error occurred.

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 UCB 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 because one of the following occurred:

• An HI command was issued with ISN less than MINISN.

• 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 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.

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

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.

This response code is issued by Event Replicator for Adabas processes. For more information, read your Event Replicator for Adabas documentation.

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.

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.

One of the following 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.

An invalid buffer length was detected by the Adabas interface routine.

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

The Adabas nucleus was either not active, or not accessible.

Refer to the hexadecimal subcode that appears in the low-order (rightmost) two bytes of the additions 2 field.

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the additions 2 field may also contain the ID of the Entire Net-Work node that issued this response code.

A command queue overflow occurred.

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the additions 2 field may also contain the ID of the Entire Net-Work node that issued this response code.

The DBA may increase the value for the NC parameter and/or the command may be issued when a lower level of command activity is in effect.

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

The DBA should increase the value of the LU parameter.

A "CALL ADABAS" was issued by a user while a previous call for the user was still being processed.

A command was rejected because it resulted in a trigger being fired, but the queue is full at this time.

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 Adabas buffer pool header blocks.

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. The leftmost two bytes of additions 2 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.

An error was detected in an inverted list index. The cause may be damage in the Associator.

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

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.

The constant set used by Adabas could not be located.

An ISN was less than the MINISN or greater than the MAXISN setting in effect for the file.

An invalid Data Storage RABN was detected.

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.

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

One of the following occurred:

• An inconsistency in an inverted list was detected.

• An internal error occurred during inverted list processing.

Run ADAICK to determine whether an inconsistency exists in an inverted list. If not, contact your local Software AG technical 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. If this response code is returned to the ADAULD UNLOAD utility function with the parameter SORTSEQ, the file might be inconsistent and data lost.

Check the file with the "check" utilities, especially ADAACK, 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.

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.

The DEUQ pool is too small.

Increase the ADARUN LDEUQP parameter.

An attempt was made to duplicate a descriptor value for a unique descriptor. The leftmost two bytes of additions 2 may contain the descriptor name.

An inconsistency in the inverted list index was found during an update operation. The leftmost two bytes of additions 2 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 or Adabas SAF Security 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:

The password specified was not found.

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.

A password pool overflow occurred.

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.

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.

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.

Logical ID greater than 255 (internal error).

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

Invalid ID table index in UB (internal error).

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

Invalid input/output buffer for internal command.

ID table not found (SVC not properly installed).

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

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

Internal command issued from Adabas version 4 Adalink.

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

Command rejected by user exit.

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

Command rejected by user exit.

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

The following table describes the subcodes that appear with this response code, clarifying why the response was received.

Increase the UB pool by respecifying the NUBS parameter in the link routines. See the ADAGSET macro information in the Adabas Installation documentation.

This response code should only occur when Adabas Transaction Manager is being used.

These response codes are reserved for Entire Net-Work.

Refer to the appropriate Software AG Entire Net-Work manuals for more information on the meanings and use of these response codes.

This response is issued by an Adabas link routine. It indicates that an ASCII-formatted user request has been issued against an EBCDIC-formatted database that is not properly configured to handle the translation:

Ensure that your Adabas installation is UES-enabled. Refer to the UES information.

This response code is reserved for Entire Net-Work.

Refer to the appropriate Software AG Entire Net-Work manuals for more information on the meaning and use of this response code.

These response codes are assigned in some Adabas user exits, and have meanings as defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4.

Refer to the description of user exits in the Adabas DBA Tasks documentation for more information.

These response codes are returned by Adabas Transaction Manger.

Consult the Adabas Transaction Manager documentation for more information.

This response code is issued for communication problems between add-on products that use the system coordinator (COR) interface to Adabas; that is, Adabas Fastpath, Adabas Vista, Adabas SAF Security, and Adabas Transaction Manager.

For subcode 1, contact your Software AG technical support representative. For subcode 2, consult the installation instructions for the add-on product.

An error occurred in Adabas cluster processing.

Under certain conditions, the Adabas cluster SVC (SVCCLU) component of the ADASVC returns response code 251 in the ACB's response code field, along with a hexadecimal subcode (listed below in decimal) in the low-order (rightmost) two bytes of the additions 2 field.

• If the local SVCCLU detects the condition, the subcode will range from 2 through 30.

• If a remote SVCCLU detects the condition, it will range from 102 through 130.

Note:
If you are running with Entire Net-Work, the leftmost two bytes of the additions 2 field may also contain the ID of the Entire Net-Work node that issued this response code.

For internal errors, contact your Software AG technical support representative. For all other errors except as noted, contact your systems administrator.

An error occurred during Adabas SVC processing (post error).

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

An error occurred during Adabas SVC processing (invalid buffer length detected).

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

The CT parameter limit was exceeded. A BT command is executed (if applicable and necessary); the command queue element and attached buffer are released; and message ADAM93 (or a similar message) is printed or displayed on the console.

If the user is not terminated, this response code is returned to the user program when an internal error occurs during processing of an attached buffer (buffer overflow). Check for one of the following subcodes in the rightmost two-bytes of the additions 2 field:

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.

All attached buffers were allocated at the time the command was processed. Buffer allocation (NAB) "high water marks" may not reflect this condition when no buffer allocation occurs.

If you were running with Entire Net-Work, the leftmost two bytes of the additions 2 field contain the ID of the Entire Net-Work node that issued this response code.