Version 4.2.6 for Mainframes (Update)
 —  Parameter Reference  —

RCA - Resolve Addresses of Static Non-Natural Programs

This Natural profile parameter controls the dynamic linking of static non-Natural programs to the Natural nucleus during initialization of the Natural session.

Possible settings ON

At Natural startup, the list of all static non-Natural programs to be linked to Natural is scanned and a load request is issued for all modules whose addresses are unresolved. If a load request fails, no error message is issued.

The use of RCA=ON is not recommended, as it causes a lot of processing overhead at Natural startup.

OFF No dynamic linking of static non-Natural programs is performed.
name-list

If RCA=name-list is specified, the list of static non-Natural programs to be linked to Natural is extended by the specified name list. A load request is issued for these modules even if they are already linked. In this way, it is possible to replace linked non-Natural programs. If a load request fails, an error message is issued.

If more than one name is specified, each must be separated from the next by a comma and the list must be enclosed within parentheses as shown below:

RCA=(PROGRAM1,PROGRAM2,PROGRAM3)

Default setting OFF  
Dynamic specification yes  
Specification within session no  

Static non-Natural programs have to be defined for being linked to Natural either internally (by using the macro NTINV within the modules NATPARM and NATCONFG) or externally (by using the profile parameter CSTATIC).

If the external name of the non-Natural program is different from the internal one (as used by the 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.

Under CICS: A PPT entry has to be defined to allow the load request for a non-Natural program. Static non-Natural programs are called via standard linkage conventions rather than EXEC CICS LINK requests.

Top of page