rdisp/scheduler/prio_high/max_runtime SAP Parameter attribute - Maximum runtime for high prio requests

rdisp/scheduler/prio_high/max_runtime is a SAP Parameter attribute which is used to control Maximum runtime for high prio requests information. This is available within R/3 SAP systems depending on the version and release level.

Below is the standard documentation available and a few details of the attributes values .

rdisp/scheduler/prio_high/max_runtime profile paramerter attributes

Parameter Name: rdisp/scheduler/prio_high/max_runtime
Description: Maximum runtime for high prio requests
Default Value: 10m
Parameter Type ( See IF_PARAMETER_TYPES): String(STRING)
Restriction Values:
Parameter Unit:
Parameter Group: Dispatcher
CSN Component: BC-CST-DP
System-Wide parameter: No
Dynamic Parameter: Yes
Vector Parameter: No
Has Sub-Parameters: No
Check Function Exists: No

Parameter documentation

This parameter limits the time for which a high-priority request can run uninterrupted in a dialog work process before it is forced to terminate. Interruptions, that is, activities that could lead to a work process switch (roll-out) (for example, COMMIT WORK, RFC call, and so on) each restart the time interval at zero. For reasons of backward compatibility, this parameter only takes effect, if the parameter rdisp/max_wprun_time is not explicitly set. The rdisp/scheduler/prio_*/max_runtime parameters 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. The system assigns high priority to all dialog requests that are directly triggered by user interaction (GUI, RFC remote logon through SM51), and to all system requests (everything that runs in the dialog work process and is not GUI, HTTP, or R FC. The intention behind this parameter is mainly defensive. It limits the consequences of an activity unintentionally running for a long time: it means that a hanging request or a programming error cannot indefinitely block a dialog work process that is intended for high priority activities. Choose a value that allows enough time for correctly-running high priority requests to be processed, even under load. 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.

See SAP Parameter Documentation for full SAP documentation for this profile parameter.