Limit Values for Resource Allocation for Asynchronous RFC 

If one of the following criteria is not met, no resources are made available for parallelization with asynchronous RFC (or triggered by the system with RESOURCE_FAILURE):

●      Number of free dialog work processes: 1
The default value is 1 and can be defined using profile parameter rdisp/rfc_min_wait_dia_wp. A certain number of dialog work processes are normally kept free as reserve instances for other purposes, such as system logon or administration programs.
It is therefore necessary to keep a greater number of dialog processes free than the number specified in profile parameter rdisp/rfc_min_wait_dia_wp.

●      Proportion of user-specific dialog work processes: 75%
You can change this default value using profile parameter rdisp/rfc_max_own_used_wp. The number of dialog work processes is set by 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 profile parameter rdisp/rfc_max_queue.
The length of the dialog queue is set by profile parameter rdisp/elem_per_queue.

●      Proportion of logons in the system: 90%
If the proportion of logged-on users already exceeds this figure, no resources will be released.
You can change this default value using profile parameter rdisp/rfc_max_login.
The maximum number of logons to a server is configured using 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 profile parameter rdisp/rfc_max_own_login. For each RFC, a logon is made in the target system.

●      Proportion of used communication entries: 90%
Each server has a limited number of communication channels at its disposal. The default limit value is 90 per cent.
You can change this value using profile parameter rdisp/rfc_max_comm_entries. The maximum number of communication channels is configured using profile parameter rdisp/max_comm_entries. Here, one entry is made for the client and one for the server for each connection.

●       

●      You can find more information under:

●      Configuration of System Resources for aRFC, tRFC, qRFC

●      Checking Authorizations for RFC