Natural RPC client and Natural RPC server support EntireX Security. This
applies to authentication against the local operating system as well as to
authentication performed by Software AG's Integrated Authentication Framework
(IAF). See the EntireX Broker attribute AUTHENTICATION-TYPE.
If a Natural RPC client or a Natural RPC server is started with
ACIVERS=8, EntireX Security without stub exits (mainframe only)
and without SECUEXIT (all platforms) are supported. In this case,
Natural issues a KERNELVERS call before any other Broker call to
get the current setting of the ACI field KERNELSECURITY. This
KERNELSECURITY setting is passed with all subsequent Broker calls.
This feature also allows a Natural RPC client to access a secured and
non-secured EntireX Broker within the same Natural session.
Natural RPC client and Natural RPC server support logging and accounting of the RPC program and the RPC library within the EntireX Broker.
The Natural RPC client provides the name of the subprogram that is to be executed and the name of the library from which the subprogram is to be executed to the EntireX Broker.
The Natural RPC server returns the name of the subprogram that has been executed and the name of the library from which the subprogram has actually been executed.
