Adabas Response Codes - Software AG Documentation

Overview of Messages
Response 168
Origin Mainframe systems only
Explanation An internal command ID required during coupling processing was not found.
Response
170
Origin Mainframe and open systems
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.
On open systems, the Additions 2 field contains the invalid RABN in 4 byte binary
format.
Action On open systems, run the LOST, INDEX and DATA options of ADAVFY for the file
in question and contact your Software AG technical support representative.
Response 171
Origin Mainframe systems only
Explanation The constant set used by Adabas could not be located.
Response
172
Origin Mainframe and open systems
Adabas Response Codes
Explanation On mainframe systems, an ISN was less than the MINISN or greater than the MAXISN
setting in effect for the file.
On open systems, the maximum possible ISN of the file was reached and no more can
be allocated.
Action On open systems, if the file contains significantly less than 2 32 records, you should
unload the file with ADAULD and reload it with ADAMUP without USERISN.
However, you must be aware that problems may arise if the ISNs have semantics for
you - if, for example, you use the ISNs to reference records in this file, additional
reorganization of these references will be necessary. The alternative to unloading and
reloading the data is to split up your data into more than one file, and to adapt your
application accordingly.
73