For static specification, this parameter is available as a
keyword subparameter of the
NTRPC
macro. For dynamic specification, this parameter is available as a keyword
subparameter of the profile parameter RPC
.
It determines which server transport protocol is used. If ACI is used, you can additionally specify the transport method.
TRANSP
is specified on the server side only.
Possible settings | ACI |
ACI is used. The transport method is defined by the EntireX Broker. |
---|---|---|
(ACI,TCP) |
ACI is used with TCP/IP. | |
(ACI,NET) |
ACI is used with Entire Net-work, i.e. using the Adabas protocol. | |
(ACI,TCP-NET) |
Trying to use ACI with TCP. If not available, ACI is used with NET. | |
(ACI,NET-TCP) |
Trying to use ACI with NET. If not available, ACI is used with TCP. | |
Default setting | ACI |
|
Dynamic specification | yes | |
Specification within session | no |
The use of TRANSP
is no longer required as you may
now specify the full node name with SRVNODE
. It is still
supported for compatibility reasons.
For further information, see the Natural Remote Procedure Call (RPC) documentation.