Adabas Response Codes - Software AG Documentation

Adabas Response Codes
Explanation The compressed record was too long. It exceeds the maximum permitted compressed
record length for the file.
On open systems, the first two bytes of the Additions 2 field contain the length of the
compressed record in binary format.
On mainframe systems, the following subcodes may be indicated:
Note:
This response code always means that the compressed record is too long and there are
duplicate meanings for subcodes but the subcode can help your Software AG technical
support representative analyze where in the code we are giving the response. This can
be useful for debugging purposes. Please always provide the subcode when
communicating about this response code with your Software AG technical support
representative.
Subcode Meaning
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.
9 Exceeded segment length maximum.
10 Long alpha or wide field.
11 New compressed record too long
12 Old version MU update.
13 The MU field was defined with an index
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.
17 MU update, MU count > 1
18 An update to an LA field caused the compressed record to become too
long.
19 LOB value too long. An attempt was made to update a LOB value
segment that ends after the maximum allowed length of LOB valus. This
response code/subcode combination is produced as a result of an L1/L4
command with Command Option 2 set to "L" but with the ISN Lower
Limit value grater than or equal to the length of the LOB value being
read.
20 Compressed Data Sorage record too long. A LOB update attempted to
make a long LOB value (greater than 253 bytes) short (less than or equal
to 253 bytes), but the base record was too long to embed the short LOB
value. This condition was detected when the LOB value was being read
from the LOB file.
21 Compressed Data Storage record too long. A LOB update attempted to
make a long LOB value (greater than 253 bytes) short (less than or equal
to 253 bytes), but the base record was too long to embed the short LOB
value. This condition was detected when an attempt was made to insert
the short LOB value into the base record.
90 Segment too long
96 Compressed record too long
99 Exceeded segment length maximum
Action On open systems, add a new DATA extent with sufficient block size (block size >=
compressed record size + 8). Alternatively you can start the nucleus with
OPTIONS=AUTO_EXPAND; then the Adabas nucleus automatically creates a new
DATA extent with sufficient block size.
24
Overview of Messages