Dynamically Configuring RFC Quotas in SAP System

 

The report RSARFCLD is used to dynamically configure the RFC quotas on the server to which you are logged on.

Unlike parameter changes in the profile, these settings are lost when you next restart the computer.

Procedure

Execute the transaction SARFC.

You are then shown which servers are currently available in the system, and how the system is handling resources for asynchronous RFCs on the servers

If you double-click on a server name, a dialog box appears in which you can change the values for your server.

If you have the necessary authorization, you can enter change mode and change the values.

The values that you set here overwrite (until the next restart) the following parameter values (in the same order):

rdisp/rfc_use_quotas

rdisp/rfc_max_queue

rdisp/rfc_max_login

rdisp/rfc_max_own_login

rdisp/rfc_max_own_used_wp

rdisp/rfc_min_wait_dia_wp

rdisp/rfc_max_comm_entries

rdisp/rfc_max_wait_time

Choose  Save to activate the new values.

Note that the settings you make using the report only apply to the instance to which you are currently logged on, and are lost when the instance is next restarted. The parameter settings in the profile file then apply again.

 

Note the following points when configuring the system:

i.The number of available resources in the system is a snapshot relating to the current workload in the system. No program can assume that these resources will also be available long term.

ii.If one of the quotas is exceeded, no resources are returned to the caller.

iii.The calculated resources are not reserved for the caller. Thus it could happen that competing programs are calculating resources at the same time, and are occupying more dialog work processes than has been set in the quota.  A program therefore cannot assume that the resources calculated are actually also available.