Parameter
rdisp/max_wprun_time
Short text
Maximum runtime for dialog requests
Parameter Description
This parameter limits the maximum runtime of a process step in a dialog process. This ensures that long-running programs do not block dialog processes and therefore prevent online operation.
After the maximum runtime has expired, the program terminates at two levels:
• If the program is currently executing ABAP commands, the ABAP processor terminates the program.
• If the program is hanging in an external command, such as SQL, the entire work process is terminated after a second time period of a maximum of 60 seconds, and the user context is reset after the process restart.
An ABAP short dump is generated in both cases.
The rdisp/scheduler/prio_*/max_runtime parameters (see below) provide the same functionality as the parameter rdisp/max_wprun_time, but allow differentiation by priorities. We recommend that you switch to the new parameters.
Application Area
Dispatcher
Parameter Unit
The unit can be specified as seconds, minutes, or hours by adding ‘s’, ‘m’, or ‘h’ . There can be spaces between the value and the unit. Specifications without a unit are interpreted as seconds. If not value is specified, the runtime is unlimited.
Examples
300 – 300 seconds
2 M – 2 Minutes
3H – 3 Hours
Are other parameters affected or dependent?
rdisp/scheduler/prio_high/max_runtime
rdisp/scheduler/prio_normal/max_runtime
rdisp/scheduler/prio_low/max_runtime
