The ADABAS database system is compatible with ORACLE. Application programs have to be precompiled using the option SQLMODE ORACLE. The SQLMODE is automatically passed to the object program. Some parts of the statements which are not operative for ADABAS generate a warning (SQLWARNF).
The SQLCODE is accepted by ADABAS, except for a few cases (see the ADABAS manual Messages and Codes).
The following conversions are done:
ADABAS Warnung3 to ORACLE -1046
ADABAS -813 to ORACLE -1034
ADABAS -4000 to ORACLE 0
ADABAS -743 in ORACLE Warning1
Isolation level 1 or 10 is set as DEFAULT. The valid isolation levels are 0, 1, 2, 3, 4.
The SQLDA structures provided by ADABAS must be included for the execution of dynamic SQL statements. The names, components, and calls within programs contained in these structures are compatible with ORACLE, but they have deviating declarations and contain additional internal information needed by ADABAS. Therefore, the corresponding include files should be used which are automatically included during precompilation instead of
EXEC SQL INCLUDE BNDDSC END-EXEC or EXEC SQL INCLUDE SELDSC END-EXEC
Descriptors defined in an application program must be adapted to the structures required by ADABAS. As the SQLDAs also contain addresses of variables, statements for address calculation must be included in addition to the declaration of the SQLDAs. These statements must have been executed before using the SQLDAs.
Include files are provided for both the declarations as well as the statements for address calculation (see the platform-specific ADABAS user manuals).
If the user wants to issue ADABAS specific statements in the application program, these have to be preceded by EXEC ADABAS instead of EXEC SQL.
For a detailed description, see the ADABAS Reference manual for the ORACLE mode.