rdisp/rfc_max_own_used_wp
Definition
This parameter determines the contingent of dialog work processes that an RFC user may occupy simultaneously. The value is specified as a percentage of the configured dialog work processes.
Use
You can use this parameter to prevent a user (or an application that is sending RFCs) from occupying all the dialog work processes on the target server.
This parameter is effective only in dialog mode. If the report is running in the background or in update mode, it is ignored.
When the server is started, it has
rdisp/wp_no_dia dialog work processes. This number can, however, be changed while the server is running. One way to do this is to use operation mode switching. You can find out the current number of processes in the Process Overview (SM50; see also
Display and Control Work Processes).
Unit: percentage
Default value: 75
Example
Let us assume that the parameter is set to the default value of 75, and you have 10 dialog work processes, of which 2 are reserved for dialog operation (
rdisp/rfc_min_wait_dia_wp). The parameter then has the effect that an RFC application can occupy a maximum of 7 work processes at any one time. This number represents the minimum number of work processes calculated from the work processes that are available for RFC (10-2=8) and the percentage defined by the parameter (75% of 10 is 7.5, of which the whole number is 7).If you want an RFC application to have all the resources on the target server, set this parameter to 100. Then,
rdisp/rfc_min_wait_dia_wp is the last restricting factor.