This Natural profile parameter controls the dynamic loading of modules that have been defined as statically linked to the Natural nucleus during initialization of the Natural session.
| Possible settings | ON |
At Natural startup, the list of all modules that have been
defined as statically linked to the Natural nucleus is inspected and a load
request is issued for all modules whose addresses are unresolved. If a load
request fails, no error message is issued.
Note: |
|---|---|---|
OFF |
No dynamic loading of static non-Natural programs is performed. | |
| module name or list of module names (see Examples below) | If a single module name or a list of module names is specified, the list of modules that have been defined as statically linked to the Natural nucleus is extended by the specified module(s). A load request is issued for the modules even if they are already linked to the Natural nucleus. This makes it possible to replace modules that have already been linked statically to the Natural nucleus. If a load request fails, an error message is issued. | |
| Default setting | OFF |
|
| Dynamic specification | yes | |
| Specification within session | no |
Notes:
CSTATIC to define modules
as being statically linked to the Natural nucleus.
CALL statement, you can use either
the profile parameter RCALIAS or the macro
NTALIAS
to define which external name is to be used for the load request.
EXEC CICS
LINK requests.
For a single module name, you may specify:
RCA=module-name
In a list of module names, each module name must be separated from the next by a comma and the list must be enclosed within parentheses:
RCA=(module-name1,module-name2,module-name3)
