Adapter Error Messages and Adabas Response Codes

In this section:

This section lists the Adabas Write Adapter error messages and common Adabas response codes.


Top of page

x
Adabas Write Adapter Error Messages

In the following error messages, the term number refers to the response code that Adabas returns. For example, the following message references Adabas error response code 113 in the Adabas Messages and Codes manual:

(FOC4561)   ERROR IN ADABAS INCLUDE/113

The following messages apply to the Adabas Write Adapter:

(FOC4555) INVALID UNQKEYNAME FOR SEGMENT
(FOC4557) ERROR IN ADABAS COMMIT/number
(FOC4558) ERROR IN ADABAS ROLLBACK/number
(FOC4559) ERROR IN ADABAS UPDATE/number
(FOC4560) ERROR IN ADABAS DELETE/number
(FOC4561) ERROR IN ADABAS INCLUDE/number
(FOC4562) RECORD IS HELD BY ANOTHER USER
(FOC4563) INCORRECT INCLUDE REQUEST FOR NON UNIQUE KEY
(FOC4564) THIS OCCURRENCE ALREADY EXISTS. USE UPDATE COMMAND.
(FOC4565) IGNORED ATTEMPT TO CHANGE NONUPDATABLE FIELD

An UPDATE command was used against a nonupdatable field, i.e. - field described in AFD as SUB/SUPERDESCRIPTOR or part of it; - field that refers in MFD to the same DB field (ALIAS) as another field (synonym case).

For individual adapter error messages, consult Adapter Error Messages.


Top of page

x
Adabas Response Codes

FOCUS Error

Adabas Response Code

Description

FOC4490

148

The database is down or unavailable.

FOC4496

148

Check the DBNO in the Access File.

FOC4500

113

The FILENO for the segment in the Access File is not correct.

FOC4504

0

Check the DBNO and FILENO in both the PREDDB and PREDEL Access Files.

FOC4504

17

The database contains no data and/or the database does not exist in the Predict dictionary.

FOC4504

28

Check the compatibility of the Predict dictionary and FDT listing.

FOC4504

41

The Predict dictionary and FDT may not match. Check the group in the FDT. It may have been created differently in the Predict dictionary.

FOC4504

201

The password is not correct.

Any

9

As a rule:

The transaction time limit (TT) or the transaction non-activity time limit (TNAE, TNAX, TNAA) has been exceeded.

For details see a subcode value in the Adabas control block's ADD2 field in the data adapter's level 3 trace, and refer to its explanation in the Adabas Messages and Codes manual.

Any

47

The maximum value for the NISNHQ parameter was exceeded.

Too many records are held. You can release them by periodically issuing the COMMIT command.

Any

40-45

One or more errors occurred in the Format Buffer.

There is a discrepancy between the Master File and the Adabas FDT.

Any

50-59

One or more errors occurred in the Record Buffer.

There is a discrepancy between the Master File and the Adabas FDT.

Any

145

An attempt was made to hold a record already in the hold queue for another user.

If variables FOCERROR or RETCODE have the value 999, the Adabas response code was not used. Use the data adapter error message to determine the cause of the error.

For details on the Adabas response codes that may accompany the Adabas Data Adapter error messages, see your Software AG publication, General Reference Set: Messages and Codes Manual. If a subcode details the specific cause and actions for the response code in this manual, you can find the subcode's value in the low-order (rightmost) two bytes of the Adabas control block's ADD2 field using the Adabas Data Adapter's level 3 trace. The trace facility for the Write data adapter is the same as for the Read data adapter.


Information Builders