This document describes how to configure the Natural RPC Server when using the IDL Extractor for Natural. It covers the following topics:
Natural RPC Server Configuration when Natural Security is not used
Natural RPC Server Configuration when Natural Security is used
Note:
Natural Wrapper is not supported under IBM i.
The Natural IDL Generator server library SYSIDL relies on the following Natural system libraries to function correctly:
| Library | Function |
|---|---|
SYSIDL |
IDL Extractor for Natural server library |
SYSRPC |
Natural RPC system library |
SYSEXT |
Natural interface library |
SYSLIBS |
Natural system library |
Depending on whether the Natural RPC Server is used in a Natural Security environment or not, steplibs are defined differently.
To define Steplibs
Specify the required steplibs in the Natural parameter module used for the Natural RPC Server. See Profile Parameters in the Natural documentation.
If your Natural user applications supported by the Natural RPC Server need more than four steplibs, a separate Natural RPC Server instance must be set up for Natural IDL generation only. You cannot use Natural IDL generation from the same Natural RPC Server instance on which your Natural user application is running. Please remember that Natural supports a maximum of eight steplibs.
In a Natural Security environment, the required steplibs must be defined in the library profile of:
the IDL Extractor for Natural server library SYSIDL
every user library from which Natural IDL generation is to be performed (see installation note 1 below).
In a Natural Security environment, clients using the IDL Extractor for Natural need to be defined in Natural Security with access to
the library SYSIDL
all libraries from which IDL generation has to be performed
If your Natural user applications supported by the Natural RPC Server need more than four steplibs, a separate Natural Security file FSEC and Natural RPC Server instance must be set up for Natural IDL generation only. You cannot use the same Natural Security file FSEC and Natural RPC Server instance on which your Natural user application is running.
You cannot use the STACK parameter to set steplibs if Natural Security
is used.
Under Natural Security, start the Natural RPC Server with
LOGONRQ=ON. If this setting conflicts with your Natural user applications, we
recommended setting up a separate Natural RPC Server instance for IDL
Generation.
Basically all parameters valid for Natural and Natural RPC Server are valid for use with the IDL Extractor for Natural server library SYSIDL.
The most important Natural RPC Server parameters to be set are:
| Parameter | Optional/Required | Explanation and Notes |
|---|---|---|
SRVNODE=<value> |
Required | The Broker ID. |
SRVNAME=<value> |
Required | The server name as defined under
SERVER under Broker Attributes.
|
TIMEOUT=55 |
Optional | Wait timeout for the Natural RPC Server. The default value 55 is suitable for most installations. It can be adapted if necessary. |
LOGONRQ=ON |
Required to be ON if Natural Security is used.
|
Forces clients to log on to Natural libraries. |
MADIO=0 |
Required | No limit on DB Calls. |
MAXCL=0 |
Required | No limit on PGM Calls. |
YSLW=1979 |
Optional, but recommended to be set. | The century of save and compile (catalog) dates of Natural
objects may be displayed incorrectly if you do not set a Year Sliding or Fixed
Window. We suggest setting a fixed window starting from 1979 on. This ensures a
correct century in the range 1979 (first release of Natural programs) up to the
year 2078. If this window setting conflicts with your application requirements,
consider
|
You will find the above parameters in your NATPARM module or you can set them dynamically.
See your Natural documentation for more information.
