This document covers the following topics:
NaturalONE runs with your own Natural Development Server (NDV) environment as an alternative to the local Natural runtime installed with NaturalONE. We recommend upgrading your Natural Development Server environment to the newest supported version. Only with the latest version will you get the complete functionality of NaturalONE.
All supported versions of the Natural Development Server can be found here:
Important
When Natural Development Server runs on a z/OS, Unicode and code page support
must be enabled (with the Natural profile parameters CFICU and CP).
Important
When Natural Development Server runs on Windows, the NaturalONE license file has
to be copied to the common/conf directory of your Natural Development Server installation
directory.
Note
Apache Tomcat is required by Ajax Developer. However, execution and debugging of rich
internet applications can be done with any application server or servlet container
supported by Natural for Ajax.
When a NaturalONE client connects to a Natural server, any startup transaction program executed on the server must meet the following conditions:
It must not perform any screen I/Os.
It must be executed only once (that is, the Natural system variable
*STARTUP must be reset to blank within the startup
transaction).
It must terminate properly.
You have to check the source code of each startup transaction in question and, if necessary, change it to meet these conditions.
If you adjust the relevant source-code sections within a startup transaction - in
dependency of the client type - you can use the Natural application programming interface
(API) USR4218N in the library SYSEXT. This API has to be invoked
from within the startup transaction and provides you with the client type.
When Natural Security is active in your Natural server environment, several actions in
the Natural Server view and in the Project
Explorer view (such as upload and download) are controlled by Natural
Security. A utility profile for SYSMAIN is then required in Natural Security
which has the appropriate settings. For detailed information, see Protecting the
Natural Development Environment in Eclipse in the Natural Security
documentation, which is part of the Natural documentation.
If the Natural Security settings are not appropriate, you may not be able, for example, to add projects from the Natural server to the NaturalONE workspace.
In order to reduce the number of Adabas calls and to improve the performance, it is
highly recommended that you create a so-called "library statistical
record" for every Natural library on the mainframe. This ensures that data
which is often used is kept persistently. Thus, when using NaturalONE, there is no need to
retrieve this specific information many times. To initialize the statistical records, you
have to invoke the program NDVCSTAR which is available on the mainframe. For
further information, see SPoD-Specific Limitations and Considerations
in the Natural Development Server documentation for the appropriate platform.
You can access Adabas databases when they are in the same environment as your NaturalONE installation.
However, remote access to Adabas database systems requires either Adabas TCP/IP communication (adatcp) or Entire Net-Work.
