Version 8.1.4
 —  Messages and Codes  —

Nucleus Response Codes

After each Adabas command is processed, a response code is returned in bytes 11 and 12 of the ACB or in the ACBX. Some response codes also return a subcode in the rightmost two bytes of the ACB's Additions 2 field (offset 45-48) or in the ACBX's Error Subcode (ACBXERRC) field (offset 115-116). This section describes those response codes and subcodes.

Note:
Proprietary functions of Adabas may also return response codes and subcodes, some of which are not described here. Refer to the documentation for those functions for more information.

Response code 0 indicates that the Adabas command was processed successfully; any other response code is returned as a result of an error during command processing.

All Adabas commands resulting in a response code other than 0, 1, and 145 restore all Adabas control block fields except the response code field (see the Adabas Command Reference documentation) to the contents the fields held at the beginning of command execution.

For internal errors, contact your Adabas technical support representative.

Overview of Messages

Response 0 | Response 1 | Response 2 | Response 3 | Response 7 | Response 8 | Response 9 | Response 10 | Response 17 | Response 18 | Response 19 | Response 20 | Response 21 | Response 22 | Response 23 | Response 24 | Response 25 | Response 26 | Response 27 | Response 28 | Response 29 | Response 34 | Response 35 | Response 40 | Response 41 | Response 42 | Response 43 | Response 44 | Response 45 | Response 46 | Response 47 | Response 48 | Response 49 | Response 50 | Response 51 | Response 52 | Response 53 | Response 54 | Response 55 | Response 56 | Response 57 | Response 58 | Response 59 | Response 60 | Response 61 | Response 62 | Response 63 | Response 64 | Response 65 | Response 66 | Response 67 | Response 68 | Response 70 | Response 71 | Response 72 | Response 73 | Response 74 | Response 75 | Response 76 | Response 77 | Response 78 | Response 79 | Response 82 | Response 83 | Response 84 | Response 85 | Response 86 | Response 87 | Response 88 | Response 89 | Response 94 | Response 95 | Response 96 | Response 97 | Response 99 | Response 101 | Response 102 | Response 106 | Response 107 | Response 109 | Response 110 | Response 113 | Response 114 | Response 123 | Response 124 | Response 125 | Response 126 | Response 129 | Response 130 | Response 131 | Response 132 | Response 133 | Response 144 | Response 145 | Response 146 | Response 147 | Response 148 | Response 151 | Response 152 | Response 153 | Response 154 | Response 155 | Response 156 | Response 157 | Response 159 | Response 160 | Response 161 | Response 162 | Response 163 | Response 164 | Response 165 | Response 166 | Response 167 | Response 168 | Response 170 | Response 171 | Response 172 | Response 173 | Response 174 | Response 175 | Response 176 | Response 177 | Response 178 | Response 179 | Response 181 | Response 182 | Response 183 | Response 184 | Response 185 | Response 197 | Response 198 | Response 199 | Response 200 | Response 201 | Response 202 | Response 203 | Response 204 | Response 207 | Response 208 | Response 209 | Response 210 | Response 211 | Response 212 | Response 213 | Response 214 | Response 216 | Response 217 | Response 218 | Response 219 | Response 220 | Response 221 | Response 222 - 223 (reserved) | Response 224 | Response 225 | Response 226 - 227 (reserved) | Response 228 | Response 229 | Response 231-239 | Response 240-244 | Response 245 | Response 248 | Response 249 | Response 250 | Response 251 | Response 252 | Response 253 | Response 254 | Response 255

Response 0
Explanation

The command was executed successfully.


Response 1
Explanation

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:

1 An online SAVE operation cannot be executed without the nucleus' PLOG.
2 The selected record is not allowed.
3 S2 command did not have enough space.
4 S2/S9 internal program error.
5 System was not in save status at the end of an online ADASAV.

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.

Action

Increase the ADARUN LS parameter value.


Response 2
Explanation

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:

1 Adabas attempted to hold an ISN already being held by another user.
2 The number of ISNs as specified in the ISN buffer was too large compared to the ISN buffer length (ET or BT command with the M option).
4 ISN is not on hold during multifetch ET/BT. ET/BT has successfully executed the ISNs so far released. The remaining ISNs are still on hold.

Response 3
Explanation

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.


Response 7
Explanation

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


Response 8
Explanation

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

Action

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


Response 9
Explanation

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:

1 The user was backed out because the hold queue was full

Action: Set the number of hold queue elements (ADARUN NH parameter) higher, or tune the application to issue more frequent ET commands.

2 The transaction time limit (TT) has been exceeded, and the transaction was backed out.

Action: Correct the cause of the timeout, then restart the transaction.

3 One of the following is the case:
  • The transaction non-activity time limit (TNAE, TNAX, or TNAA) has been exceeded.

  • The user was stopped by the STOPF or STOPI operator, or an Adabas Online System command.

  • A security violation response code has been returned for an ET-logic user. Information about response codes for security violations is provided in the Adabas Security documentation.

  • When a new user issues an OP cmd with the same user ID (in ADD1) as an earlier user did and the earlier user was inactive for more than 60 seconds, the new user can, by issuing a second OP cmd again (the first OP cmd will get response code 9, subcode 64), take over the user ID of the earlier user. When the earlier user becomes active again, this subcode can be received.

Action: Correct the cause of the timeout, then restart the transaction.

15 The user was backed out because a pending Work area overflow occurred during this operation.

Action: Either reduce the transaction length to lessen the data protection area requirement, or increase the protection area on Work.

17 At the end of an online recovery process that was initiated after the failure of a peer nucleus in an Adabas cluster, the nucleus was unable to reacquire the ETID specified by the user in the Additions 1 field of the OP command.

Action: (In the application program:) Redo the OP command with the ETID specified in the Additions 1 field to reacquire the user ID. Contact your Software AG technical support representative.

18 The user's active transaction was interrupted and backed out because a peer nucleus in an Adabas cluster terminated abnormally.

Action: (In the application program:) Rerun the transaction.

19 The user's active command was interrupted and stopped because a peer nucleus in an Adabas cluster terminated abnormally. If the interrupted command was using a command ID (CID), the command ID is deleted.

Action: (In the application program:) Clean up and reacquire the current context pertaining to Adabas command IDs; rerun the transaction.

20 The Adabas cluster nucleus assigned to the user terminated while the user had an open transaction. The transaction has been or will be backed out.

Action: (In the application program:) If the user was defined with a user ID (ETID) in the Additions 1 field of the OP command, redo the OP command to reacquire the ETID; clean up and reacquire the current context pertaining to Adabas command IDs; rerun the transaction.

21 The user's active command was waiting for an ISN in hold status when the user was backed out and closed due to a timeout or a STOP command.
22 The user's active command was waiting for free space in the work pool when the user was backed out and closed due to a timeout or a STOP command.
62 An OP (open) command was issued without a user/ET ID, which is required for this type of application or environment.

Action: Correct the program to specify a user/ET ID, and rerun the program.

63 An OP command was given for an ET user not in ET status. The user is backed out with an Adabas-generated BT command, and the operation is closed.

Action: Repeat the OP call.

64 An OP command was issued with an 8-byte ET ID that already exists.
66 An Adabas session with OPENRQ=YES was active and the user issued an Adabas command without having issued an OP command.

Action: Ensure that all users issue an OP command as the first Adabas command.

67 Insufficient Work part 1 space for open command with ETID definition when trying to read the user profile.
68 The user queue element has been deleted. Most likely the command was thrown back due to ISN contention or space shortage. The space shortage is normally workpool space; if this is the case, the LWP parameter setting should be increased.
73-78 These subcodes are given only when Adabas Transaction Manager is in use. Review the Adabas Transaction Manager documentation for more information.
79 Used by Adabas System Coordinator to signal the (optional) terminal timeout. Review the Adabas System Coordinator documentation for more information.
80-99 These subcodes are given only when Adabas Transaction Manager is in use. Review the Adabas Transaction Manager documentation for more information.
130 In a cluster, the UQE of the user was deleted between the time the user's command was routed to one nucleus in the cluster and the time that nucleus selected the command for processing.
249 This subcode is given only when Adabas Vista is in use. Review the Adabas Vista documentation for more information.

Response 10
Explanation

Too many occurrences for a periodic group.


Response 17
Explanation

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:

1 The program tried to access system file 1 or 2, and no OP command was issued.

Action: Restructure the program to begin with an OP command.

2 The program tried to access system file 1 or 2, and the user is not authorized.

Action: Change the program to avoid the access.

4 One of the following occurred: - The specified file number is invalid. - When running with ADARUN DTP={RM | TM}, an attempt was made by a non-ATM user to access/update an ATM system file.
5 The file is either not loaded, or has been locked by another user for privileged use. For ADAORD and ADAINV utility operations, the write phase has started and use of the file is now blocked for the type of operation you requested.
6 An E1 (delete record) command was given without specifying a valid file number.
7 The program tried to perform an LF command on system file 1 or 2.
8 The program tried to access a file that was not listed in the file list of an open (OP) executed with the R option.
9 The file that the program attempted to access is completely locked. This is usually because the maximum number of logical file extents that can fit into the FCB have been used.

Action: Reorder, then unlock the file. Continue operation.

10 The program attempted to access a file which is locked with exclusive EXU status.
11 An LF command (read FDT) was run on a file that is not loaded; neither the FCB nor the FDT exists.
12 File has been locked with LOCKF.
13 A file is password-protected and the password was specified, but the corresponding security file is missing (not loaded).
14 A command was issued against a LOB file. Commands involving LB fields should be directed against the base file, not the LOB file.
15 A file is being loaded so its information is temporarily unavailable.
16 An attempt was made to perform an update (e.g. A1, E1, N1/2) against a file loaded with the attribute RPLUPDATEONLY=YES.
18 File has been locked with ALOCKF.
21 Not enough space for encoding elements (ECSE).
22 The required ECS objects needed for conversion between user and system data representation could not be loaded.
23 ECS object could not be located. The following objects must be available in the encoding objects library: File Alpha, File Wide EDD, User Alpha, User Wide EDD, and the PTOs for the combinations between file/user alpha/wide encodings.

Action: Check that the required EDD and PTO objects are available.

24 ECS function get_attribute() failed.

Action: The function's return code is logged with the nucleus message ADAN7A.

25 One of the following occurred: - A required encoding attribute was missing in an ECS object (encoding type, class, and flags) - The default space character length was > 4 - Default space table allocation failed - If DBCS-only plane exists, wide space character was undefined, or the length > 4, or wide space table allocation failed
29 An Adabas Review communication error has occurred. Contact your Software AG support representative.
249 This subcode is given only when Adabas Vista is in use. Review the Adabas Vista documentation for more information.

Response 18
Explanation

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


Response 19
Explanation

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


Response 20
Explanation

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

  • X'00000000'

  • X'40404040'

  • X'FFxxxxxx'

User Action:

Avoid usage of any of the above command ID values.


Response 21
Explanation

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.


Response 22
Explanation

The command 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, 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:

1 The nucleus detected an invalid command code.

Action: Correct the command code, and rerun the program.

2 This command cannot be issued by an ACC (access only) user.
3 This command cannot be performed on a read-only nucleus.
4 This privileged command was issued without a previous OP (open) command.
5 The command is not valid for a nonprivileged user.
6 The command was rejected by user exit 1.
7 Incorrect command options were specified for a privileged command.
8 The command is invalid for an ET user in preliminary ET status. First complete the transaction using Adabas Transaction Manager.
9 The current user is not authorized to issue an ET/BT command.
10 The C2 command is no longer permitted.
11 The C3 command can only be issued by EXU users.
12 The L1/4 command with the option "F" is not valid for expanded files.
13 The call issued is not permitted when the database is in a suspend state.
14 Invalid privileged command.
15 An L1 command specified the multifetch option "M" or "O" combined with either the "I" or "N" option.
16 The user does not have "privileged" command authorization.
17 Not permitted during online save.
18 Applications using the ADALNK X'48 call logic receive this response when the logic has been suppressed.
21 ET command is invalid for a distributed transaction managed by Adabas Transaction Manager.
22 The current transaction has already been heuristically terminated.
23 BT command is invalid for a distributed transaction managed by the Adabas Transaction Manager.
24 CL is invalid because the user has a transaction in progress that is managed by Adabas Transaction Manager.
25 A command was sent from an Event Replicator Server to an Adabas nucleus, but the Adabas nucleus is not running with ADARUN REPLICATION=YES.
26 An attempt was made by an Adabas nucleus to connect to an Event Replicator Server when the target of the message is actually another Adabas nucleus, not an Event Replicator Server.
28 A replicated utility may not be executed for a replicated file when the Adabas nucleus is running in single-user mode.
29 An error occurred during a connection attempt by an Event Replicator Server database. Ensure that you are trying to connect to another Adabas nucleus and not an Event Replicator Server and try again.
32 An attempt was made to update a replicated file in single-user-mode. Replicated files can be updated only in multi-mode; replication is not supported in single-mode. However, a nucleus with replication support can be started in single-mode for maintenance purposes.
50 The Router (LCC) detected an invalid command code. This may also arise when a new ACBX-type call is presented to a back-level router.

Response 23
Explanation

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.


Response 24
Explanation

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.


Response 25
Explanation

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


Response 26
Explanation

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.

2 An S9 command with an ISN buffer contains ISNs that are higher than the TOP-ISN of the file.

Response 27
Explanation

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.

1 Sufficient work space was not available to generate the format translation.

Response 28
Explanation

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.


Response 29
Explanation

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.


Response 34
Explanation

An invalid command option has been detected.

Action

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


Response 35
Explanation

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


Response 40
Explanation

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.

  • Subcode 9: Selective format not allowed with multiple buffers


Response 41
Explanation

One or more specification errors exist in the format buffer. When possible, the short name of the field for which the error occurred is stored at offset 2 of the ACB's Additions 2 field or in the ACBX's Error Character Field (ACBXERRB). The following specification errors may have been made:

1 A phonetic descriptor or hyperdescriptor was specified.
2. A field specification error occurred:
  • The specified field name is reserved for edit masks.

  • The field is not in the selected file.

3 An indexing error occurred:
  • No index was specified for a periodic-group name or field.

  • A group or multiple-value field index greater than the allowed maximum was specified. In Adabas versions prior to Version 8, this maximum is "191"; in Adabas version 8 or later, this maximum is "65,534".

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

4 A periodic-group error occurred:
  • 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.

5 A group error occurred: a group reference specified a length/format.
6 A multiple-value field error occurred:
  • 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.

7 The descriptor name not found in FDT/SDT.
8 A length indicator (fldL) or asterisk notation (fld,*) is not allowed for field fld (for example, when fld is a superdescriptor or subdescriptor field)
9 1-N or x-N range notation is not permitted for elementary large object (LB) fields in a periodic group.
10 An LB field is not permitted in an L9 command.
11 A length indicator (fldL) or asterisk notation (fld,*) is not allowed for field fld (for example, when fld does not have the LA or LB option)
12 The old MU syntax is not allowed for LB fields.
13 A length indicator (fldL) or asterisk notation (fld,*) is not allowed with a count indicator (fldC) or field range (for example, AA-ZZ)
14 The length indicator (fldL) and asterisk notation (fld,*) are not allowed together (for example, fldL,*)
15 A length indicator (fldL) or asterisk notation (fld,*) is not allowed with a significance operator (for example, fldS).
User Action:

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.


Response 42
Explanation

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

1 The Work pool was too small to store a user format.

Action: Increase the LWP specification and retry .

2 The internal format buffer was too small to store a user format (translated into internal structure).

Action:Increase LFP specification and retry.


Response 43
Explanation

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


Response 44
Explanation

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

1,3 The format buffer specification was invalid (conditional format buffers are not allowed for update operations).
2,4 The L9 command's format buffer format is not allowed for other commands.
5 The L9 command specified a conditional format in the format buffer.
6 A floating-point field was addressed using a length other than 4 or 8; or a fixed-point field was addressed using a length other than 4.
7 Conditional format and more than one format buffer was specified.
8 The current Adabas call provides a different number of format buffers than the format reference by CID.

Response 45
Explanation

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.

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


Response 46
Explanation

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


Response 47
Explanation

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


Response 48
Explanation

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.

1 A specified file is locked against the requested use.
2 A specified file is currently in conflicting use.
3 A utility cannot start because an online save operation is in progress.
5 A utility requiring exclusive database control cannot start because an online save operation is in progress.
6 A utility that requires exclusive database control cannot start because the user queue is not empty.
8 The user ID specified in the open command is already in use by another user.
9 An EXU/EXF/UTI lock was requested in the open command, but the file is currently in the file list of a user in UPD/EXU/EXF/UTI status.
10 An EXF/UTI lock was requested in the open command, but the file is currently in the file list of a user in ACC status.
11 A nonprivileged user issued an open command to a nucleus in UTIONLY status.
13 Online file save attempting to run on an advance-locked file.
14 UPD/ACC open attempted against advance-locked file.
15 A file requested for an online utility (Adabas Online System or ADADBS) or an E1 program refresh is currently being used.
16 ACODE or WCODE was specified in the record buffer on the command but the nucleus was not activated with UES support.
17 A specified file is locked against the requested use and is advance-locked.
18 A second command was issued by a user who is participating in a two-phase commit (preliminary ET completed; final ET outstanding) or whose transaction has been heuristically terminated.
19 The file number is zero or is greater than the maximum number of files allowed for the database (based on the MAXFILES parameter setting when the database was defined using the ADADEF utility).
20 A regenerate/backout with exclusive database control is rejected because there are in-doubt transactions or heuristically terminated transactions on Work part 4.
21 File is locked for utility usage.
25 - 30 Reserved for Adabas Transaction Manager. These subcodes are given only when Adabas Transaction Manager is in use. Please see the Adabas Transaction Manager documentation for more information.
31 File locked for normal usage
32 A file is in use by an exclusive update (EXU) user. An update request from another user is not permitted.
33 A file is locked for exclusive file control (EXF) or utility update (UTI) usage. The request from a user with a different type is not permitted.
257 - 260 Reserved for use by Event Replicator for Adabas on open systems.

Response 49
Explanation

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

1 Multiple-value (MU) field.
2 Periodic (PE) group field.
3 MU field.
4 PE group.
5 PE group level.
6 Remaining fields.
7 Record too long for protection logging (internal error).
8 A compressed record exceeds the permitted length. The error was detected when updating a multiple field.
10 Long alpha or wide field.
14 An MU update caused the compressed record to become too long.
15 An MU update caused the compressed record to become too long.
16 An MU update caused the compressed record to become too long.
18 An update to an LA field caused the compressed record to become too long.

Response 50
Explanation

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


Response 51
Explanation

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


Response 52
Explanation

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

1 Invalid packed or unpacked decimal value in record buffer.
2 Invalid length for variable-length field specified in record buffer.
3 Invalid null value or no value at all provided for field with NN option.
4 Invalid value for S element in record buffer.
5 Invalid value for S element in value buffer.
6 Encoding a collation descriptor value failed: the collation descriptor exit issued a return code.
7 Decoding a collation descriptor value failed: the collation descriptor exit issued a return code.
99 An invalid field length was specified.

Response 53
Explanation

One of the following errors occurred (the leftmost column indicates the subcode):

0 The record buffer is too small.

Action: If the record buffer size

  • conflicts with the lengths specified in the format buffer, change either the record buffer size or the format buffer specifications to resolve the conflict.

  • conflicts with the established global format ID (GFID), either release the GFID or change the record buffer size to match the GFID.

  • default is too small to hold the records in the file including the DVT when running the ADAULD utility, increase the size of the record buffer by setting the ADAULD LRECL parameter. See the Adabas Utilities documentation for more information.

2 The ISN buffer is too small.

Action: Increase the size of the buffer.

7 At least one of the record buffers was too small for the data defined in the corresponding format buffer. EDEERE contains the buffer number in error.
8 The referenced existing format buffer requires more space than that given in one of the record buffers.

If this subcode occurs using ADACMP DECOMPRESS, the LRECL of the output record is too small.

249 This subcode is given only when Adabas Vista is in use. Review the Adabas Vista documentation for more information.

Response 54
Explanation

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:

1 The record buffer for the C3 command is too long.
2 The record buffer for the C5 command is too long.
3 The record buffer for the ET command is too long.
User Action:

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


Response 55
Explanation

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.

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


Response 56
Explanation

One of the following occurred:

. The descriptor value was too long; or
n The collation value exceeded the maximum 253 bytes. The subcode "n" is the collation descriptor exit number.

Response 57
Explanation

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


Response 58
Explanation

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


Response 59
Explanation

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


Response 60
Explanation

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.

1 Format buffer length is invalid.
2 Invalid syntax element in the search buffer.
3 Missing start/ending apostrophe for literal value.
4 Literal of zero bytes.
5 Invalid delimiter or missing period.
6 Missing close parentheses ")".
7 Empty criterion: soft coupling or conditional format.
8 Invalid second character in a "FN" definition.
9 Edit mask number greater than 15.
10 Invalid character following field name specification.
11 Invalid form of case ABN(xxx)/ AB3(xxx)/ AB3-6(1-4).
12 More than 8 digits for a numeric value is not permitted.
14 Invalid L element definition.

Response 61
Explanation

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

Subcode Meaning
3 An invalid logical operator was specified for an S8 command - Command Option 2.
7 This subcode indicates that one of the following errors occurred:
  • The length of a descriptor value was greater than 253.

  • Invalid file number specification.

  • Invalid selection criteria for an Event Replicator for Adabas initial-state definition.

  • Invalid usage of the "S" or "N" operator.

  • The element order was invalid.

  • The specified field was not a descriptor.

  • The specified field has the "LA" option active.

  • A descriptor contained in a periodic group was specified without an index.

  • Invalid connection of partial criteria or different indices were used for a descriptor contained within a periodic group.

  • Invalid periodic group index.

  • Invalid or disallowed use of a phonetic descriptor.

  • A descriptor derived from or contained in a periodic group is not allowed.

  • The FROM-TO operator was specified with a phonetic descriptor.

  • Invalid FROM-TO range specification, or the FROM value was greater than the TO value.

  • The BUT-NOT value was outside the range of the preceding FROM-TO range.

  • An invalid command option was specified for ISN LIST processing (S8 command).

  • The search buffer "S" significant null indicator was specified with a value operator other than "EQ" (equals), which is not allowed.

8 An invalid FROM-TO range was specified. The BUT-NOT value was outside the range of the preceding FROM-TO value.
9 An invalid search criteria was specified.

Response 62
Explanation

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


Response 63
Explanation

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


Response 64
Explanation

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.

Action

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.


Response 65
Explanation

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


Response 66
Explanation

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


Response 67
Explanation

One of the following errors occurred:

. An internal error occurred while executing an Sx command.
2 An error occurred during superfield generation.
Action

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


Response 68
Explanation

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").

Action

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.


Response 70
Explanation

An overflow occurred in the table of sequential commands.

Action

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


Response 71
Explanation

An overflow occurred in the table of resulting ISN lists.

Action

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


Response 72
Explanation

One of the following errors occurred:

7 An overflow occurred in the user queue.
8,9 An overflow occurred in the user queue file list pool.
Action

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


Response 73
Explanation

An overflow occurred in the section of the Work data set in which resulting ISN lists are stored.

Action

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.


Response 74
Explanation

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

Action

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.


Response 75
Explanation

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

Action

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


Response 76
Explanation

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


Response 77
Explanation

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

1 FST empty.
2 AC START RABN not available.
3 AC END RABN not available.
4 FST will not fit into five ASSO blocks.
5 FST exhausted trying to allocate AC extent.
6 ASSO space allocation RABN not on device.
7 ASSO space on required device not available.
8 FROM RABN available, but contiguous space is not sufficient.
9 Data Storage space of the requested size is not available.
10 Data Storage space on the same device as the previous extent is not available.
11 FST is empty, or data storage for the current MAXRECL value is not available.
12 FST empty.

Response 78
Explanation

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

1 The AC file cannot be increased; only one file extent is permitted.
2 The file contains more than either 4 billion or 16 MB of ISNs, depending on the ISN length.
Action

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.


Response 79
Explanation

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

1 Either a collation descriptor exit (subcode 'CDX'n where n is the one-byte binary collation descriptor exit number) or a hyperdescriptor exits ("hyperexit") was not specified ADARUN.
5 The hyperexit stub was called for an extended MU/PE file.
6 Improper use of the parameter list was detected by the Hyperexit Stub. The most likely reason is that a hyperexit using the Adabas 8 parameter structures is linked to the Hyperexit Stub.
7 The Hyperexit Stub could not resolve the HEXOLD external reference.
8 Improper use of the parameter list was detected. The second word of the parameter list was modified.
9 A hyperexit did not return an output parameter area address.
10 A hyperexit rejected the call by setting a nonzero return code in the output parameter header.
Action

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

1 Reissue ADARUN with the CDXnn or HEXnn parameter. For more information about ADARUN parameters, read Adabas Initialization (ADARUN Statement), in Adabas Operations Manual; for more information about user exits and hyperexits, read User Exits and Hyperexits, in Adabas User, Hyperdescriptor, and Collation Descriptor Exits Manual.
5 The Hyperexit Stub may not be used with extended MU/PE files. For more information about hyperexits, read User Exits and Hyperexits, in Adabas User, Hyperdescriptor, and Collation Descriptor Exits Manual.
6,7 Investigate the Hyperexit Stub link job. For more information about hyperexits, read User Exits and Hyperexits, in Adabas User, Hyperdescriptor, and Collation Descriptor Exits Manual.
8 A likely cause of the error is that a pre-Adabas 8 hyperexit was called without a linked Hyperexit Stub. For more information about hyperexits, read User Exits and Hyperexits, in Adabas User, Hyperdescriptor, and Collation Descriptor Exits Manual.
9 Hyperexits must return an output parameter area address upon return. For more information about hyperexits, read User Exits and Hyperexits, in Adabas User, Hyperdescriptor, and Collation Descriptor Exits Manual.
10 Investigate the hyperexit to determine why the call was rejected.

Response 82
Explanation

A hyperexit routine returned an invalid ISN.


Response 83
Explanation

Hypertable overflow.


Response 84
Explanation

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


Response 85
Explanation

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


Response 86
Explanation

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.


Response 87
Explanation

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

Action

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

1 Check the LBP value with DPARM.
2 Increase the ADARUN LBP parameter value;
3 Retry the operation. If the error recurs, call your Software AG support representative for assistance.

Response 88
Explanation

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 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 subcodes and provides recommended actions.

Subcode Operation Encountering the Workpool Shortage Action
1 Only active command is waiting for workpool space. Increase the ADARUN LWP setting and try again.
During session autorestart, insufficient workpool or user queue space was encountered. Increase ADARUN LWP and NU parameter settings and try again.
2 Only active command is waiting for workpool space. Increase the ADARUN LWP setting and try again.
3 A command waiting for workpool space was interrupted for transaction backout.
4 A1 command
5 E1 command
7 Superfield value generation
8 N1 command
9 OP command
10 Descriptor value generation
11 Hyperdescriptor value generation
12
13 Subdescriptor value generation
15 DTP=RM: A getmain error during Work-Part-4 initialization.
16 Hard-coupled file update processing encountered a workpool shortage.
17 A session autorestart encountered a workpool shortage.
22 Online reorder by descriptor
23 Online invert
24 Work I/O buffers for session autorestart in cluster (offline/online recovery)
25
80 Spanned record processing
96 Internal command queue full
98 Cluster with DTP=RM: Recovery of distributed transactions encountered a workpool shortage.
99 ET command with P-option
Descriptor value generation for multi-client file
Single-user mode: Command initialization
Replication: Setup of initial-state process
DTP=RM: Insufficient user queue space during Work-part-4 initialization Increase the ADARUN NU setting and try again.
Action

Review the actions described in the table above.


Response 89
Explanation

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


Response 94
Explanation

An I/O error occurred on DDWORKR4.


Response 95
Explanation

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


Response 96
Explanation

An error occurred during ADARES REPAIR utility execution.

2 An I/O error occurred during nucleus termination; Additions 2 may contain RABN.

Response 97
Explanation

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


Response 99
Explanation

An I/O error occurred.


Response 101
Explanation

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.


Response 102
Explanation

Space calculation error.

Action

Retry the open operation.


Response 106
Explanation

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


Response 107
Explanation

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


Response 109
Explanation

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


Response 110
Explanation

The command ID pool is full.

Action

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


Response 113
Explanation

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.

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


Response 114
Explanation

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

Subcode Description
1 A file refresh is not permitted for the file (PGMREFRESH=NO) or the command ID field (ACBCID or ACBXCID) is not all blanks.
2 The user has not completed transactions to the file. Updates have been performed or records are still in hold, but the user has not issued an ET or BT command to commit or back out the updates.
3 Other users are accessing or updating the file. This is determined by the user access or update counts available internally to Adabas.
4 The file is a multiclient file and the user is not a superuser.

Response 123
Explanation

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:

Subcode Description
4 No valid destination(s)
8 Too many destinations
12 Invalid message type
16 Invalid environment
20 Send buffer length exceeded
24 Receive buffer length exceeded
28 No replies or acknowledgment(s) before the message timed out. For more information about the timeout value, refer to descriptions of the ADARUN MXMSG parameter.
32 Unable to allocate AXMCB
36 Timed out on originating system
40 Timed out on destination system
44 Cancelled on destination system
48 Receive error on destination system
52 Unable to allocate buffer
80 Messaging is inactive
96 Terminate member unsuccessful
128 Other transport service error
Action

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


Response 124
Explanation

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.

Action

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


Response 125
Explanation

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.

Action

Contact your Software AG technical support representative.


Response 126
Explanation

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.

Action

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


Response 129
Explanation

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


Response 130
Explanation

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

Subcode Description
1 A user table entry (UTE/PLXUSER) was not found in the MPM 8 call. This may indicate that a command was directed to an Adabas Cluster Services or Adabas Parallel Services nucleus ID (NUCID), not the DBID.
2 A user table entry (UTE/PLXUSER) was not found in the MPM 12 call.
3 A command queue entry (CQE) was not found in the MPM 8 call.
4 An intermediate user buffer (IUB) was not found in MPM 8 call.
5 An Adabas control block not found in MPM 8 call.
6 An invalid UTE/PLXUSER was found on the nucleus chain .
7 An invalid UTE/PLXUSER was found on the user chain add.
8 An invalid UTE/PLXUSER was found on the "lura" chain (that is, the linked list of UTEs representing local users remotely assigned) delete.
23 An invalid CQE was found.
Action

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.


Response 131
Explanation

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:

Code Meaning

1 The combination of URBD plus payload data does not fit in the output buffer.
Action: Change the subscription definition to make the record shorter.
2 The subscription user exit set a value in URBRERRC.
Action: Check the URBRERRC field and correct the error if appropriate.
3 There is insufficient space in the nucleus replication pool. In other words, the value specified by LRPL has been exceeded.
Action: Increase the LRPL size of the nucleus and try again.
4 There is insufficient space in the Event Replicator Server replication pool. In other words, the value specified by LRPL has been exceeded.
Action: Increase the size of the LRPL parameter and try again.
5 The subscription user exit modified data length (URBDLEND) to an invalid value.
Action: Check the subscription user exit.
6 The response destination (URBIRNAM) specified in a client request is undefined or not usable for sending the response.
Action: Correct the status request to specify the name of an existing destination definition.
7 Both the subscription (URBISNAM) and the destination (URBIDNAM) to be specified in a status request are missing. At least one of them must be specified.
Action: Correct the status request.
8 The subscription (URBISNAM) specified in a status request is undefined.
Action: Correct the status request.
9 The initial state name specified was not found.
Action: Correct the initial-state request.
10 The destination for response in URBI following URBI 1 is not equal to those of URBI 1.
Action: Correct the initial-state request.
11 The initial state name in URBI following URBI 1 is not equal to that of URBI 1.
Action: Correct the initial-state request.
12 The combination of DBID and file specified in the initial-state request is not found in the initial-state definition.
Action: Correct the initial-state request.
14 Not all combinations of DBID and file are specified in the initial-state request. A URBI must be sent for each DBID/file specified in the initial-state definition.
Action: Correct the initial-state request.
15 Field URBILEND is invalid.
Action: Correct the initial-state request.
16 The specified ISNLIST is invalid.
Action: Correct the initial-state request.
17 The initial-state process has been stopped by an operator request.
Action: No action is required.
18 Different request tokens have been specified in different URBI elements in the same message.
Action: Correct the initial-state request.
19 Selection data is not allowed for an initial-state definition for all records or for destination open/close client requests.
Action: Correct the initial-state or destination open/close client request.
20 Invalid input data for decompression was found during the subscription phase.
Action: Check the index of the replicated file.
22 The file/DBID supplied for the initial-state process is deactivated for replication.
Action: Check the cause of deactivation and repeat the request after reactivation.
23 Invalid UES parameter in URBI . URBIARC, URBIACOD, and URBIWCOD must contain invalid values and must not be all blanks.
Action: Verify that the URBIARC, URBIACOD, and URBIWCOD elements are not all blanks.
24 Invalid UES parameter in URBI.
URBIARC, URBIACOD and URBIWCOD must be zero for input requests where encoding and architecture is not evaluated -- that is, for status requests, destination open/close requests, "initial state all records" or "initial state ISN list" requests.
Action: The URBIARC, URBIACOD, and URBIWCOD elements must be zeros for "initial state all records" requests, "initial state ISN list" requests, status requests, or destination open/close requests. Verify that this is the case.
25 The unused URBIRES1 and URBIRES2 fields must contain binary zeros for all requests.
Action: Verify that these fields contain binary zeros.
26 The destination (URBIDNAM) specified in a client request is either undefined or not usable for sending the response.
Action: Correct the client request.
27 No active destinations for status request.
Action: No action is required.
28 An initial-state request was issued to an Event Replicator Server address space that was terminating as a result of an ADAEND or HALT command. An initial-state request may only be issued when the Event Replicator Server is active.
Action: Reissue the initial-state request when the Event Replicator Server has been restarted.
30 Unknown response destination name in URBIRNAM for a prior-transaction request.
Action: Correct the prior-transaction request.
31 Unknown destination name in URBIDNAM for a prior-transaction request.
Action: Correct the prior-transaction request.
32 Unknown or omitted subscription name in URBISNAM for a prior-transaction request.
Action: Correct the prior-transaction request.
33 Destination in URBIDNAM is not related to subscription in URBISNAM for a prior-transaction request.
Action: Correct the prior-transaction request.
34 Subscription in URBISNAM has no resend buffer defined for a prior-transaction request.
Action: Correct the prior-transaction request.
35 Transaction in URBITSNR for subscription in URBISNAM was not found in the resend buffer. The transaction may have been overwritten in the circular resend buffer.
Action: Check the source of the transaction number.
36 The subscription in URBISNAM is not active.
Action: No action is required.
37 An invalid transaction was found in the resend buffer. This is an internal error.
Action: Notify your Software AG technical support representative.
38 There are no active destinations for a prior-transaction request.
Action: No action is required.
39 URBILEND must be zero for prior-transaction requests.
Action: Correct the prior-transaction request.
40 URBIDBID and URBIFNR may not be specified for this type of client request.
Action: Correct the client request.
41 URBIINAM may not be specified for prior-transaction requests.
Action: Correct the prior-transaction request.
42 UES parameters URBIARC, URBIACOD and URBIWCOD may not be specified for prior-transaction requests.
Action: Correct the prior-transaction request.
43 Reserved fields URBIRES1 and URBIRES2 must be zero for prior-transaction requests.
Action: Correct the prior-transaction request.
44 Number of active concurrent initial-state requests exceeded IMAXREQ.
Action: Increase the IMAXREQ setting or reduce the number of active concurrent initial-state requests.
45 Input request URBH eyecatcher is invalid.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
46 Input request URBHLEN is invalid.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
47 Input request URBHBORD is invalid.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
48 Input request URBHVERS is invalid.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
49 Input request message truncated.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
50 Input request URBHLENT is invalid.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
51 Input request URBILENH is invalid.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
52 Input request URBILEND is invalid.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
53 Input request URBILEN is invalid.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
54 Input request reserved area is not zero.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
55 Input request more than one status received.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
56 Input request invalid URBI request received.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
57 Input request different interleaved requests received.
Action: Verify that you are submitting only one kind of request to the Event Replicator Server. Only one type can be submitted at a time (for example, you cannot request initial-state processing and transaction status information requests in the same message).
Correct the input information and try again. For more information, read Event Replicator Client Requests in Event Replicator for Adabas Application Programmer's Reference .
58 Invalid destination for response.
Action: Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference .
59 A replay request was issued for a database not defined to the Event Replicator Server.
Action: Correct the DBID in the replay request or define the database to the Event Replicator Server.
60 Invalid replay token. The replay token is not defined or is outdated.
Action: Specify a valid replay token.
61 Invalid request sent to Event Replicator Server. RBL is insufficient, no FB provided on initial handshake or other such errors.
Action: Notify your Software AG technical support representative.
62 After an Adabas failure and session autorestart, replication data was recovered for which a matching FDT was no longer available. The FDT had been changed or deleted by a utility operation. Adabas suppressed the record images of the replicated records, because without a matching FDT, the Event Replicator Server could not process them.
Action: Use application-specific means to bring the replicated data in sync again, if necessary.
63 The file specified in a C5 command with R-option is not replicated.
Action: Specify the file number of a replicated file.
64 The filter defines a comparison between two field types for which a comparison is invalid.
Action: Correct the filter definition.
65 The filter refers to a field that is not defined in the internal format buffer.
Action: Correct the filter definition or define the field in the database.
66 The filter defines a comparison against a field that is not selectable as it has no type (for example, a superdescriptor).
Action: Correct the filter definition.
67 The filter uses values in an FLIST specification that are invalid or out of range.
Action: Correct the filter definition.
69 Replay for same DBID/FNR already running.
71 Date/time format or value incorrect for replay.
Action: Check the syntax of the specified date and time values. Do not specify future date and time values.
72 Incorrect replay parameters.
Action: Check and correct the specified replay parameters.
73 A subscription involved in the replay was inactive at the beginning of replay processing or was deactivated while the replay was running.
Action: Reactivate the deactivated subscription and rerun the replay process for the subscription.
74 A destination involved in the replay was inactive at the beginning of replay processing or was deactivated while the replay was running.
Action: Reactivate the deactivated destination and rerun the replay process for the destination.
75 A replay destination that was defined without SLOG was closed at the beginning of replay processing or while the replay was running.
Action: Reopen the closed destination and rerun the replay process for the destination.
76 ADARPL terminated abnormally.
Action: Investigate the cause of the error, correct it, and run a new replay job.
77 Invalid replay status transition. Events that change the status of a replay process occurred in an unexpected order.
Action: Notify your Software AG technical support representative.
78 New transactions from Adabas could not be kept on hold during a replay in synchronized mode.
Action: Run a new replay process involving the same subscriptions and destinations as the previous replay process to recover the replication data that Adabas produced while the first replay was running.
79 A replay process was canceled by a user (RPLCLEANUP operator command).
Action: If appropriate, run another replay job with corrected parameters.
80 A timeout occurred while the Event Replicator Server was waiting for the end of a synchronization process after reactivating replication for a file in Adabas. The synchronization process ends when all transactions have finished that had updated the file before it was reactivated.
Action: Wait until the Event Replicator Server reports the activation of the file (ADAF2L message). Then run a new replay job.
81 A utility other than ADARPL specified a replay token when connecting to the Event Replicator Server.
Action: Notify your Software AG technical support representative.
82 The Event Replicator Server is not connected to Adabas at the start of a replay process with the TOKEN parameter.
Action: Start Adabas and let it connect to the Event Replicator Server. When running a replay with the TOKEN parameter, Adabas must be active.
83 Neither a subscription nor a destination was specified in a replay request.
Action: Specify at least one subscription or destination.
84 A replay in replay-only mode was requested, but replication data from Adabas would flow through an active subscription-destination pair involved in the replay. For a replay in replay-only mode, some subscriptions and destinations must be inactive such that no data from Adabas can flow through the same subscription-destination pairs as the replay data from ADARPL.
Action: Change the replay parameters or the activation status of the subscriptions or destinations involved in the replay.
85 A file involved in the replay was inactive at the beginning of the replay or deactivated while the replay was running.
Action: Reactivate the deactivated file and rerun the replay process for the subscriptions involved in the replay that get data from the file.
86 Invalid format buffer was specified for destination-type Adabas update commands
Action: Correct the format buffer.
87 An unexpected message sequence number was encountered.
Action: Contact your Software AG support representative.
88 An unrecognized eye-catcher was encountered in control block following the URBH.
Action: Contact your Software AG support representative.
89 The same subscription name was specified more than once for an Adabas automated replay (defined using the Adabas Event Replicator Subsystem or Event Replicator Administration).
Action: Verify that a subscription is specified only once in an automated replay, and try again.
90 The same destination name was specified more than once for an Adabas automated replay (defined using the Adabas Event Replicator Subsystem or Event Replicator Administration).
Action: Verify that a destination is specified only once in an automated replay, and try again.
91 The replay start date and time were not supplied for an automated replay (defined using the Adabas Event Replicator Subsystem or Event Replicator Administration) or for multiple destination open/close client requests.
Action: Verify that a destination is specified only once in an automated replay or in multiple destination open/close client requests and try again.
92 The timeout parameter specified for an automated replay was too high.
Action: Reduce the timeout parameter value and try again.
93 PLOG information was not recorded in the Event Replicator Server system file.
Action: Contact your Software AG support representative.
94 The AI/BI format buffer was used also for the key. An attempt was made to decompress a key value, but the related format buffer is for data storage and not for a key.
Action: Contact your Software AG support representative.
95 An attempt to set user/Event Replicator Server encoding 01-RPEQU * failed. This might occur if you are using enhanced filtering logic and UES SACODE/SWCODE/SARC values are set for a subscription.
Action: Contact your Software AG support representative.
96 The Adabas nucleus that was the target of an initial-state request returned response code 148, indicating it is not available.
Action: Start the targeted Adabas nucleus and retry the initial-state request.
99 The subscription name (URBISNAM) specified in the destination open/close client request contains a value other than spaces.
Action: Correct the destination open/close client request by setting this field to spaces.
100 The transaction sequence number (URBITSNR) specified in a destination open/close client request contains a value other than binary zeroes.
Action: Correct the destination open/close client request by setting this field to binary zeroes.
101 The destination open/close request failed on some tasks.
Action: Investigate the cause of the error.
102 The destination open/close request failed.
Action: Investigate the cause of the error.
103 The destination open/close request was not performed because the destination's status was already in the state being requested. In other words, the destination was already opened or closed.
Action: No action is required.
104 Begin byte in field filter is longer than the field length.
Action: Adjust the specifications for the beginning byte or length and try again.
105 Begin byte plus the portion length in the field filter is longer than the field length.
Action: Adust the specifications for the beginning byte or the portion length and try again.
106 Begin byte or length not supported for field with format U, P, F, G, or W.
Action: Specifying a beginning byte or length is only supported for alphanumeric and binary fields. Change the field on which you are working or abandon this attempt.
107 Length value invalid for field.
Action: Adjust the length specification and try again.
108 Input request URBI eyecatcher is invalid.
Action:Correct the input information and try again. For more information, read Event Replicator Client Requests in the Event Replicator for Adabas Application Programmer's Reference.

Response 132
Explanation

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.

Subcode Description
8 A LOB file operation was aborted due to a pending backout of the user's command or transaction. One reason for this backout may be that the user's transaction occupied too much space on the protection area on the Work data set (see response code 9, subcode 15).
17 The LOB file is not loaded.
48 The LOB file is locked for exclusive read or update by another user.
65 An internal error in the work pool space calculation occurred for LOB file processing.
113 A LOB file segment record was not found in the Address Converter element referred to by the LOB file index. Either the LOB file is physically inconsistent or an illegal concurrent LOB file update occurred during the LOB file read operation.
145 An attempt failed to put a LOB file segment record on hold for a user, because it was already held by another user. This subcode indicates illegal update contention for the same large object field value. The base file-LOB file pair is possibly inconsistent.
165 The LOB file descriptor is not found in the index; The LOB file index is bad.
172 An ISN in the LOB file index is bad. The LOB file may be physically inconsistent.
175 The descriptor value in a LOB file segment record differs from the descriptor value in the LOB file index. Either the LOB file is physically inconsistent or an illegal concurrent LOB file update occurred during the LOB file read operation.
177 A LOB file segment record was not found in the Data Storage block referred to by the Address Converter. Either the LOB file is physically inconsistent or an illegal concurrent LOB file update occurred during the LOB read operation.
257 An error in the base file-LOB file linkage exists; a file with LB fields is not really the base file of the LOB group.
258 An error in the base file-LOB file linkage exists; the file linked to the base file of a LOB group is not really a LOB file.
259 An error in the base file-LOB file linkage exists; the LOB file linked to a base file of a LOB group refers back to a different base file (or none at all).
260 An error in the base file-LOB file linkage exists; either no LOB file was linked to a base file or the LOB file number is invalid.
261 The LOB file has been left in an inconsistent state by an aborted utility execution.
262 An LB field length element specification error occurred in the format buffer ('xxL,4,B' was expected).
263 An invalid LOB file segment descriptor was encountered. The set of LOB file segment records associated with one LB field value is inconsistent. Either the LOB file is bad or an illegal concurrent LOB file update occurred during the LOB file read operation.
264 An invalid LOB file segment record was encountered. The contents of a LOB file record are inconsistent. The LOB file is bad.
265 The length of an LB field value in the LOB file differs from the length stored in the associated base file record. Either the base file and the LOB file are out-of-sync or an illegal concurrent LOB file update occurred during the LOB file read operation.
266 A bad LB field value reference was encountered in a base file record. The base file is bad.
297 A planned feature for large object (LB) fields (for example, character code conversion of LB field values) is not yet supported.
298 Too many (more than 32,767) LB field occurrences were specified in the format buffer.
299 An internal error occurred due to LOB file processing.

Response 133
Explanation

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

Subcode Description
1 The function is not permitted for this type of file. The file is a LOB-file.
2 The compressed input record length is invalid .
11 The record structure is invalid.
12 An invalid elementary empty field was encountered. The structure does not agree with the FDT definition.
13 An invalid multiple-field count was encountered.
14 An invalid periodic group count was encountered.
15 An invalid structure of an elementary field was encountered.
65 A space calculation error occurred.

Response 144
Explanation

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.

Action

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.


Response 145
Explanation

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.

Subcode Description
0 N2 command for an existing ISN was issued.
1 Hold queue space problem detected. The user is the only active user and is running with the -R option.
2 The ISN was held by someone else. The read request is running with the -R option.
9 Two or more users became deadlocked while holding ISNs and attempting to put more ISNs in hold status.

Response 146
Explanation

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:

Subcode Buffer Type
1 Format buffer
2 Record buffer
3 Search buffer
4 Value buffer
5 ISN buffer
6 User information buffer
7 Performance buffer
8 Multifetch buffer

Response 147
Explanation

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


Response 148
Explanation

The Adabas nucleus was either not active, or not accessible. 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:

Subcode Description Action
1 Exclusive database control requirement conflicts with read-only nucleus status. Remove the READONLY=YES parameter setting for the nucleus and restart it.
2 A nonprivileged call was made to the nucleus while it was in utility-only (UTI) mode. Remove the UTIONLY=YES parameter setting for the nucleus and restart it.
3 The nucleus is performing shutdown processing (an ADAEND operation) and will not accept new users or new transactions. Either a new user is attempting to begin operation or an existing user in ET status is trying to continue operation. Wait for the nucleus to shut down, restart it, and reissue the command.
4 A utility with exclusive database control is running. Either stop the utility or wait for its processing to complete (this is preferred) and try again.
5 A single-user nucleus could not start operation due to an error that could not be corrected. Verify that single-user mode has been set up correctly and restart the nucleus.
8 A user is performing a logical ADALNK call. The IDT for the call has not been allocated. On BS2000 systems, check the setting of the parameter accessed by the link name DDLNKPAR or DDCARD, or in the macro B2CONFIG of the module SSFB2C. Also check the IDTNAME parameter of the database to be accessed.
50 At command completion RSP148 was set but without a subcode. This subcode is set to indicate the command was processed by the target. Contact your Software AG support representative for assistance.
51 The command router found no suitable target. The target was determined not to be an Adabas Cluster Services or Adabas Parallel Services database. Contact your Software AG support representative for assistance.
52 The command router found no suitable target. The target was determined to be an Adabas Cluster Services or Adabas Parallel Services database. Contact your Software AG support representative for assistance.
53 The command router found a suitable target but the target became inactive while queuing the command. Contact your Software AG support representative for assistance.
54 When the caller attempted to retrieve the results of a completed command the target was no longer active. Contact your Software AG support representative for assistance.
55 The target became inactive while the caller was attempting to retrieve the results of a completed command. Contact your Software AG support representative for assistance.
101/201 Set in SVCCLU when a specifically designated local nucleus is not available for a physical call. The 201 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.
102/202 Set in SVCCLU when a specifically designated remote nucleus is not available for a physical call. The 202 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.
103/203 Target ID disagreement between IDTE and PLXNUC. The 203 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.
104/204 Unable to find PLXMAP matching an existing PLXUSER. The 204 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.
105/205 Entire Net-Work unavailable, can't route existing user to remote nucleus. The 205 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.
106/206 Entire Net-Work unavailable, can't route new user to remote nucleus. The 206 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.
107/207 No nucleus available for remote user. The 207 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.
108/208 Incorrect PLXMAP update received by LOCAL=YES nucleus. The 208 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.
109/209 An internal command used to synchronize across multiple nodes was received for an Adabas Parallel Services database. Such databases may execute on only one node. Depending on intersystem communications timing this may occur as a database is changed from Adabas Cluster Services to Adabas Parallel Services. Otherwise this is a logic error. Contact your Software AG support representative for assistance.
110/210 Unable to assign specified nucleus to remote user. The physical command arrived via Entire Net-Work for a specific nucleus, but the specified nucleus is on another system. Only one Entire Net-Work transmission is allowed. The 210 subcode appears when this subcode is set on a remote node. Contact your Software AG support representative for assistance.

Response 151
Explanation

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.

Action

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.


Response 152
Explanation

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

Action

The DBA should increase the value of the LU parameter.


Response 153
Explanation

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


Response 154
Explanation

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

Action

Retry the command.


Response 155
Explanation

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

Action

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


Response 156
Explanation

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

Action

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


Response 157
Explanation

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.

Action

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.


Response 159
Explanation

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.

Action

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.


Response 160
Explanation

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


Response 161
Explanation

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


Response 162
Explanation

No additional space is available for Adabas buffer pool header blocks.


Response 163
Explanation

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


Response 164
Explanation

Too many work areas were allocated for the command.


Response 165
Explanation

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


Response 166
Explanation

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


Response 167
Explanation

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


Response 168
Explanation

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


Response 170
Explanation

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.


Response 171
Explanation

The constant set used by Adabas could not be located.


Response 172
Explanation

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


Response 173
Explanation

An invalid Data Storage RABN was detected.


Response 174
Explanation

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


Response 175
Explanation

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.

Action

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


Response 176
Explanation

Either an inconsistence in an inverted list was detected or an internal error occurred during inverted list processing. The following possible subcodes are associated with this response code:

Subcode Description
2 Bad index
3 Invalid search request
4 Invalid format indicator or field not found in FDT/SDT
11 Invalid search request
12 Bad index block
13 Bad UI block
14 Mismatch block length
15 Bad MI block
16 Mismatching block length
17 Bad NI block
18 Bad ISN count
21 Bad index block
22 Mismatching block length
23 Invalid ISN count
29 Inactive index block
31 Bad index block
32 Mismatching block length
33 Invalid ISN count
39 Inactive index block
41 Bad index block
42 Mismatching block length
43 Bad MI block
44 Bad NI block
81 Invalid level indicator
82 Bad element position in block
83 Position in block did not match element lengths
84 Bad MI block
85 Bad NI block
86 Bad NI block
87 Invalid ISN count
88 Position in block did not match element lengths
89 Index block not active
91 Wrong level
92 Mismatching block length
Action

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.


Response 177
Explanation

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.

Action

Check the file with the "check" utilities, especially ADAACK, and contact your Software AG technical support representative.


Response 178
Explanation

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

1 Inconsistency in descriptor value table (DVT).
2 An inconsistency was detected between the field definition table (FDT) and the internal format buffer.
3 Inconsistency when updating a phonetic descriptor.

Response 179
Explanation

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


Response 181
Explanation

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


Response 182
Explanation

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


Response 183
Explanation

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


Response 184
Explanation

A phonetic field name could not be found.


Response 185
Explanation

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


Response 197
Explanation

The DEUQ pool is too small.

User Action:

Increase the ADARUN LDEUQP parameter.


Response 198
Explanation

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.


Response 199
Explanation

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.


Response 200
Explanation

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:

0 A standard user check failed.
1 There is no free user file cache entry for a workstation user.
2 A cross-level security check failed.
3 No security information is available for the command.
4 A timeout occurred during a workstation logon.

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


Response 201
Explanation

The password specified was not found.


Response 202
Explanation

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

User Action:

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


Response 203
Explanation

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


Response 204
Explanation

A password pool overflow occurred.


Response 207
Explanation

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.

User Action:

Send a phase 2 logon request to Adabas SAF Security.


Response 208
Explanation

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.

Action

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.


Response 209
Explanation

Adabas SAF Security detected an expired password on the server.

Action

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


Response 210
Explanation

Logical ID 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.


Response 211
Explanation

Invalid ID table index in UB (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.


Response 212
Explanation

Invalid input/output buffer for internal command.


Response 213
Explanation

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:

Subcode Description
16 The specified SVC number does not correspond to a currently installed SVC on the z/OS or VSE system. Check to be sure that the specified SVC number is correct and, if it is, ensure that an Adabas SVC is installed using that SVC number.
20 The specified SVC number corresponds to an installed SVC on the z/OS or VSE system, but the SVC is not an Adabas SVC. Ensure that the provided SVC number is correct and, if it is, determine why the SVC installed for that number is not an Adabas SVC for z/OS or VSE.
User Action:

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


Response 214
Explanation

Internal command issued from Adabas version 4 Adalink.


Response 216
Explanation

Command rejected by user exit.

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.


Response 217
Explanation

Command rejected by user exit.

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.


Response 218
Explanation

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

Subcode Description
X'00' (00) The UB (TP monitor user block) pool is too small. There must be at least one user block for each concurrent user. This is controlled by the TP monitor link routines. The GETMAIN for the UB failed.
X'48' (72) An IPC message call parameter error occurred. This may indicate an internal product error or a TP-monitor storage overlay. Contact Software AG technical support for assistance.
X'49' (73) The IPC message caller did not provide a pointer to the extended user ID block. This is probably an internal product error. Contact Software AG technical support.
X'4C' (76) The extended user ID data provided to the IPC Message Call is either binary zeroes or blank. This is probably and internal product error. Contact Software AG technical support.
X'4D' (77) A getmain failed for the work area used in an IPC Message Call. Determine why the TP monitor is running short of storage. The storage will be acquired in the AMODE of the calling program, usually 31-bit for Natural transactions.
User Action:

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


Response 219
Explanation

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

2 The global transaction is not in the status that allows the call.
3 Two transaction ID (XID) entries exist.
4 The "R" and "J" options are not supported; or this is not a global transaction. The transaction ID (XID) does not exist or cannot be found (or example, when the given XID does not belong to the UQE).
5 The record or value buffer definition may be invalid; for example, the length size may be invalid (less than or equal to 144 bytes); or the value buffer content may be invalid; for example, it may not contain a valid transaction ID (XID).
6 The user is not an update or ET user or is already involved in a global transaction or the user is already on PET (preliminary end-of-transaction) status.
7 A protocol error occurred: The user has been copied to Work 4 or the transaction was backed out.
8 A protocol error occurred: The transaction was terminated or the user has no transaction ID (XID) or the recover call for an active user is not permitted.
9 The system is currently locked due to a pending Work area 4 or DDWORKR4 overflow.
10 The call is not permitted; either ADAEND or an ET-sync point is in process for the nucleus. Force the ATM nucleus to backout (BT) the transaction.
11 The user has not made any updates. A preliminary ET command, therefore, is not permitted.
12 A logic error occurred.
20 The transaction ID (XID) is unknown. This error occurs only in a cluster environment.

Response 220
Explanation

The request was rejected by Entire Net-Work due to a shortage of short term buffers.

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.

Action

For BS2000 systems running Sockets 2.2 or later, check the address space limit using the SHOW-USER-ATTRIBUTES command in the field ADDRESS-SPACE-LIMIT (the value is in megabytes). If necessary, increase it using the MODIFY-USER-ATTRIBUTES command from a privileged user ID.

For BS2000 systems running Sockets 2.1 or earlier, increase the CMSIZE parameter to enlarge the common memory pool, as long as there is enough room in the address space. Then restart Entire Net-Work.

For z/OS and z/VSE, increase the region size. For z/VM, increase the amount of virtual storage available to the Entire Net-Work machine.


Response 221
Explanation

The LU size of the remote partner is smaller than the size required for the Adabas request.

Action

Either increase the size specified for the LU= parameter on the remote system, or modify the application to reduce its buffer sizes.


Response 222 - 223 (reserved)

Response 224
Explanation

The request waited for a reply for a longer time period than specified by the REPLYTIM parameter in either the NODE statement or the SET operator command. The reply may be delayed or lost due to a target malfunction, or because of a connecting link failure. If you are using Natural, and all connections are verified, check the ADAMODE setting. The ADAMODE=0 setting is the only option Entire Net-Work supports.


Response 225
Explanation

A command was issued from a server, such as an Adabas nucleus, to another server, such as Entire Net-Work. The command did not complete within a prescribed time period. The issuer proceeds and no longer expects a response to the command.

Note that the command may still execute in the target. There will be no notification to the issuer if it does. The target may display message ADAM92, User Gone, if the target attempts to notify the issuer of command completion.

The subcode identifies the environment from which the command was issued.

Subcode Issuer
1 ADAMPM
2 Adabas nucleus, thread-synchronous command
3 Adabas nucleus, not thread-synchronous. Under z/OS, the command was TCB-synchronous.
Action

Contact your Software AG technical support representative for assistance if the reason for the command's failure to complete cannot be identified.


Response 226 - 227 (reserved)

Response 228
Explanation

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:

1 The SVC is not a valid Adabas version 7 SVC.
2 The database is not UES-enabled.
User Action:

Ensure that your Adabas installation is for a supported version and that the database is UES-enabled. Refer to the UES information.


Response 229
Explanation

The Entire Net-Work 5 convertor detected an inconsistency or error in the application format buffer or search buffer and is unable to correctly translate the user's data.


Response 231-239 –
Explanation

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.

User Action:

Refer to the description of user exits in the Adabas User, Hyperdescriptor, and Collation Descriptor Exits Manual documentation for more information.


Response 240-244 –
Explanation

These response codes are returned by Adabas Transaction Manager. Consult the Adabas Transaction Manager documentation for more information.


Response 245
Explanation

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.

Subcode Description
1 Internal error.
2 A required module could not be loaded. This is probably an installation error.
Action

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


Response 248
Explanation

These response codes are returned by Adabas Data Archiving processing. Review the Adabas Data Archiving documentation for more information.


Response 249
Explanation

This response code is given only when Adabas Vista is in use. Review the Adabas Vista documentation for more information.


Response 250
Explanation

The ACBX (ACBX) failed validation. The following subcodes are possible:

Subcode Description
1 Unsupported ACBX version
2 ADACBX provided without UBE.
3 ACBX file number > 65,535.
4 Reserved field not zero.
5 ACBX length incorrect
Action

If subcode 3 occurs, notify your Software AG technical support representative. If any of the other subcodes occur, correct the ACBX specification and rerun.


Response 251
Explanation

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. In the case of an ACBX, the ADASVC returns response code 251 in the ACBX's Response Code (ACBXRSP) field and the subcode in the Error Subcode (ACBXERRC) 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 (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.

Subcode Description
2 The remote cluster nucleus to which the user is assigned cannot be accessed.
4 There are no user table entries (UTEs) available for use.
5 Internal error. The nucleus specified by an internal command was not found.
7 Internal error. The user was assigned to a remote nucleus by the local system but the remote system found that the nucleus was not active.
9 Internal error. The 28-byte user ID is all zeros.
17 Entire Net-Work is not active.
19 Internal error. Invalid internal command code.
20 Remote nuclei are active; command must be assigned remotely but the remote nuclei are not accepting commands.
21 The remote image to which the user is assigned has no usable nuclei.
22 An attempt was made to assign a user remotely but Entire Net-Work is not active.
25 No system image target
26 System image target changed
27 Internal error.
28 Version mismatch between the PLXCB and the SVCCLU part of the ADASVC.
29 Probably, you used a NUCID value from a restricted range. Otherwise, this is an internal error.

Action: Ensure that the NUCID assignments are valid.

30 More than 32 NUCIDs were detected for the same SVC/DBID combination.

Action: Reduce the number of NUCIDs on the SVC/DBID to 32.

Action

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


Response 252
Explanation

An error occurred during Adabas SVC processing (post 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.


Response 253
Explanation

An error occurred processing a buffer.

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 subcodes are possible:

Subcode Description
0 Buffer length 0 (ACB user only)
1 Format buffer address zero
2 Record buffer address zero
3 Search buffer address zero
4 Value buffer address zero
5 ISN buffer address zero
6 User information buffer address zero
7 Performance buffer address zero
8 Multifetch buffer address zero
9 Unsupported ABD buffer type
10 Attached buffer overrun
11 Unsupported ABD version
12 ACBX not accepted by target
13 Unable to convert ACBX to ACB
14 ALET value not permitted
15 Unable to process 64-bit buffer address
16 Invalid buffer location indicator
17 Logic error locating ABD
18 More than 32,767 ABDs
19 Reserved field not zero
20 ADABDX length incorrect
Action

Subcodes 10 and 17 are internal logic errors; notify your Software AG support representative. For all other subcodes, correct the buffer specification error and rerun.


Response 254
Explanation

A validation error occurred during command completion processing while attempting to return results to the caller.

One of the following has occurred:

  • An internal error occurred during processing of an attached buffer (buffer overflow)

  • The CT parameter limit was exceeded. Message ADAM93 (or a similar message) is printed or displayed on the console.

    If the CT parameter limit was exceeded, the nucleus terminated the user, generated the equivalent of a BT command internally, released the CQE and attached buffer space, and issued ADAM93 (or a similar message).

    If the user was not terminated, the subcode in the right-most two bytes of the ACB's Additions 2 field or the subcode in the ACBX's Error Subcode (ACBXERRC) field describes the failed validity check.

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.

Subcode Description
1 UBCQEX is less than or equal to zero
2 UBCQEX is greater than CQHNCQES
3 CQEFLAG is not equal to CQEFAB plus CQEFW16
4 CQEAUB is not equal to A'UB
5 CQEAUPL is not equal to A'APL
6 The low-order 6 bytes of CQECKSUM does not equal UBCKSUM
7 CQE was timed out
8 An inconsistency in the CQE such as the following: The CQE was unexpectedly taken by another call The user buffer (UB) is not receiving expected user information The target move data length is inconsistent
9 Record buffer overflow
10 ISN buffer overflow
11 Inconsistent format buffer length
12 Inconsistent search buffer length
13 Inconsistent value buffer length
14 Inconsistent user buffer length
15 Invalid attached buffer ABD index (internal logic error)
16 Buffer overflow; see ACBXERRD and ACBXERRE
Action

Ensure that the caller’s control structures and parameters are not altered while the command is being processed. If you are unable to resolve the error, notify your Software AG support representative.


Response 255
Explanation

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.

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.


Top of page