In this parameter you can set the level of detail of the check made by the RFC server dispatcher. The dispatcher checks whether sufficient dialog work processes are free for processing asynchronous RFC calls.
The number of available dialog work processes depends on the number of free dialog work processes and on the number of work processes that must be kept free for the dialog application. (Compare with rdisp/rfc_min_wait_dia_wp).
If no work process is free, the request is placed in the queue and processed later.
The RFC resource check is active (see rdisp/rfc_use_quotas).
Work area |
Dispatcher/task handler |
Unit |
Integer value |
Standard value |
1 |
Dynamically changeable |
Local and on all servers |
The parameter can be set to a whole number between 0 and 3. The number specifies the level of the resource check. The values mean the following:
Level 0: No check is run
Level 1: Monitors the start of all asynchronous RFCs
Level 2: Monitors, additionally to level 1, all RFCs started anew from asynchronous RFC sessions. This includes synchronous RFCs.So that applications that transmit a lot of RFCs can run at this level, the number of dialog processes used for RFCs may have to be increased. (rdisp/rfc_min_wait_dia_wp may have to be reduced).
Level 3: monitors all RFCs (synchronous and asynchronous).
You must not set the value to 0.
Increase the value if you notice that your application server becomes flooded with RFCs and dialog mode is no longer possible, even though you have set rdisp/rfc_min_wait_dia_wp.
Note the following documentation associated with this parameter:
RFC Resources in the Application Server
Monitoring RFC Resources on the Application Server
Problems with RFC Resource Assignment
Configuring the SAP System for Parallel RFCs