This document describes how to prepare Natural in order to use it with Adabas.
The following topics are covered:
The Adabas ADALNK access method is the classic access method based on IPC communication.
The database can either be accessed locally or remote via Entire Net-Work. The ADALNK method is used, when no specific connect string is provided in the parameter section of an Adabas DBID in the global configuration file and hence the ADALNK method is the default method.
If you want to use the ADATCP access method for connecting an Adabas database there are some prerequisites:
Your Adabas version must support the ADATCP access method.
The Adabas database to be accessed must have been enabled for ADATCP.
Please refer to your Adabas documentation and especially to the section Adabas Remote Database Access for further details about how to setup your databases correctly.
In order to access such an ADATCP-enabled Adabas database you need to add a connect string for some Adabas DBID in the parameter section of the Natural global configuration file.
To access an ADATCP-enabled Adabas database
Invoke the Natural Configuration Utility (NATPARM).
Select Natural Configuration Files > Global Configuration File > Database Management System Assignments > DBMS Assignments.
Select the DBID you want to enable for ADATCP access and assure that the type is set to ADA or ADA2.
In the parameter section, enter the connect string in a
format like
adatcp://<fqdn>:<port>
where <fqdn> is the fully
qualified domain name of the server hosting your database and
<port> is the port number which
has been defined for that database's ADATCP listener.
For a complete description of the connect string syntax, please refer to the section Adabas Remote Database Access in the Adabas documentation again.
Save the global configuration file.
From now on, all requests for that specific Adabas database are performed via ADATCP. Please note, that it is not necessary to recatalog your Natural application to use ADATCP. And of course, you can access one DBID via ADATCP and some other DBID via ADALNK at the same time.
Note:
Because the ADATCP interface only supports Adabas calls in ACBX
format, all other database calls in ACB format are automatically converted to
ACBX before being sent and converted back to ACB when being returned to
Natural.