This document covers the following topics:
With Natural Version 6.3.4, a new database driver ADA2 is delivered that supports features introduced with Adabas 6 (Open Systems) and Adabas 8 (mainframe). This includes support of Adabas large objects fields, Adabas LA fields and extended Adabas buffer lengths.
See also Adabas Database Management Interfaces ADA and ADA2 in the Programming Guide.
The following new Natural parameter is provided in this version:
| Parameter | Description |
|---|---|
DO |
Specifies how fields are to be interpreted for display on terminals that support bidirectional data. |
An enhanced logging information system is now provided. See Logging Information in the Natural Web I/O Interface documentation.
In addition to editing the configuration file nwosrvd.conf, it is now also possible to configure the Natural Web I/O Interface daemon by specifying commands at the UNIX command prompt. See Natural Web I/O Interface Daemon Commands in the Installation documentation.
The prerequisite for using the Natural Web I/O Interface client on a Java EE-based server has changed. It is now required that Java Runtime 5 or above is installed.
It is now possible to define a different trace directory for IIS.
It is now possible to enable tracing for a session on a Java EE-based server
(Sun Application Server and JBoss Application Server). To do so, you set the
trace attribute in a session definition to
"true".
In case of problems with the Natural Web I/O Interface client or Natural for Ajax on a Java EE-based server, you can now enable logging and thus write the logging information to an output file. See Logging in the Natural Web I/O Interface documentation.
The following changes are planned for future versions of Natural.
With Natural Version 6.3.4, the database driver ADA is still used by default.
With a future version of Natural, the default setting for the database driver will change to ADA2.
With a future version of Natural, the handling of the
TF parameter will be
changed.
Currently, it is only possible to use the asterisk (*) notation for the database ID (DBID) and file number (FNR) of the production database. In a future version, it will also be possible to use the asterisk notation for the database ID and file number of the test database. It may then be possible that your applications will behave in a different way.
