Limit Values for Resource Allocation for Asynchronous RFC
If one of the following criteria is not fulfilled, no resources are made available for the parallelization with asynchronous RFC (or triggered by the system in the exceptional case RESOURCE_FAILURE):
·
Number of free dialog work
processes: 1
The default value is 1 and can be defined using the profile parameter
rdisp/rfc_min_wait_dia_wp. As standard, a certain number of dialog work
processes are kept free as reserve instances for other purposes, such as
system logon or administration programs.
For this reason, a greater number of dialog processes must be free, than the
number specified for the profile parameter rdisp/rfc_min_wait_dia_wp.
·
Proportion of user-specific
dialog work processes: 75%
You can change this default value using the profile parameter rdisp/rfc_max_own_used_wp. The number of dialog work processes is
defined using the profile parameter rdisp/wp_no_dia.
·
Proportion of requests waiting in
the dialog queue: 5%
You can change this default value (5% of the total length of the dialog queue)
using the profile parameter rdisp/rfc_max_queue.
The length of the dialog queues is defined using the profile parameter
rdisp/elem_per_queue.
·
Proportion of logons in the
system: 90%
If the proportion of logged on users already lies above this, then no
resources are released.
You can change this default value using the profile parameter rdisp/rfc_max_login.
The maximum number of logons to a server is configured using the profile
parameter rdisp/tm_max_no.
·
Proportion of separate logons in
the system: 25%
You can change this default value (25% of all logons) using the profile
parameter rdisp/rfc_max_own_login. For each RFC, a logon to the target system
takes place.
·
Proportion of used communication
entries: 90%
Each server has a limited number of communication channels available. The
default limit value is 90 per cent.
You can change this value using the profile parameter rdisp/rfc_max_comm_entries. The maximum number of communication channels
is configured using the profile parameter rdisp/max_comm_entries. Here, one entry for each connection is made for
the client and server.
Checking Authorizations for RFC