Parameters for D19, Q19, P10, DA2, QA2
Parameters for D19, Q19, P10, DA2, QA2...
Sheet1 Parameters List rdisp/scheduler/prio_low/max_quota rdisp/scheduler/prio_normal/max_quota rdisp/scheduler/prio_low/max_runtime rdisp/scheduler/prio_normal/max_runtime rdisp/scheduler/prio_high/max_runtime rdisp/max_wprun_time SAP Kernel Version
80% -60 m 10 m 600 749 – 218
80% -60 m 10 m 3600 749 – 218
80% -60 m 10 m 3600 749 – 218
80% -60 m 10 m 600 749 – 200
Note: Scheduler run time parameters only become effective if the parameter rdisp/max_wprun_time is not explicitly s It is recommended to migrate to the new parameters if the system is on SAP Kernel 7.40 and above. rdisp/wp_no_dia rdisp/scheduler/prio_low/max_quota rdisp/scheduler/prio_normal/max_quota
18 13 15
Sheet1 QA2 70% 80% -60 m 10 m 600 749 – 200
wprun_time is not explicitly set.
Maximum quota of work processes used for low prio requests. The parameter limits the maximal number of low priority reques Maximum quota of work processes used for normal or low prio requests
Max. run time depends on priority:medium and high priority sessions currently have defaults at one hour resp. 10 minutes.
s not explicitly set.
Sheet1 priority requests that can be processed in parallel
2129291 - Session Priority and Work Process Q A request is the smallest unit of activity in the ABAP application server. Each request belongs to a session and derives its priority from it. Requests are created either by external sources (SAP GUI, HTTP client, RFC client) or internally by work processes. The objective of the kernel scheduler is to distribute requests to work processes according to priority.
All activities in the ABAP application server is associated with the sessions. Sessions may be long-lived (e.g. a traditional SAP GUI session) or short-lived (e.g. a stateless HTTP request or a technical re Multiple sessions may be bundled together in one logon (only used by SAPGUI, where multiple "external mode" belongs to th Sessions can be identified uniquely by their session key, which is shown in SM50, SM04 and other monitoring transactions, e. Starting from SAP Kernel 7.4x, each session is assigned a unique session type based on the way the session was created Each session type comes with a default priority class Session types cannot be changed during the lifetime of a session.
Priorities are assigned to sessions based on their session type. There are three priority classes: high, medium and low. The general concept is to assign high priority for activities that are directly related to user interaction, low priority for backgroun The low priority of batch requests is inherited by any RFCs started by the batch session, i.e. such RFCs also get low priority
Before SAP Kernel 7.40, profile parameter rdisp/rfc_min_wait_dia_wp or rdisp/http_min_wait are used for determine the m profile parameter rdisp/rfc_min_wait_dia_wp and rdisp/http_min_wait_dia_wp determines the maximum number of work p Starting from SAP Kernel 7.4x, Scheduling within the application server has been changed with the introduction of request prio There are specific scheduler parameters (with the prefix "rdisp/scheduler") for the configuration profile parameters rdisp/scheduler/prio_low/max_quota and rdisp/scheduler/prio_normal/max_quota to assign quotas fo you are able to achieve the same configuration for work process quota with the old profile parameters (i.e. profile parameters
The ABAP application server has always employed the concept of a maximum runtime per dialog request, i.e. limiting the max Activities that could potentially trigger a "roll-out" (e.g. COMMIT WORK, RFC call, ...) restart the timer at zero. This is intended as a defensive mechanism to protect against unintentionally long dialog requests. Without such a safety mechanism, any malfunctioning code in a session (blocking or looping ABAP code) would block a dialog
The quota parameters allow for fine-tuning of scheduler behavior. They should be used with care, and only if there is a clear indication that the resulting change of behavior is understood and fo the kernel scheduler distributes requests strictly according to priorities (highest first).
The parameter rdisp/scheduler/prio_low/max_quota limits the maximal number of low priority requests that can be processed Even if there are free work processes and no requests with higher priority, the kernel scheduler will never use more work proc Note that this parameter aggregates the number of normal and low requests It cannot be configured lower than rdisp/scheduler/prio_low/max_quota, resulting in the desired "at most normal priority" sema
The intention behind this maximal quota is to limit the number of concurrently executing low or normal priority requests, effecti Quotas can be configured as fixed numbers or percentages of work processes (by appending '%'). No quota is used if the value is empty. The concept of maximum run times has been introduced Their intention is to protect against sessions monopolizing the precious common resource 'work process' The value must always be chosen so that 'normal requests' have enough time to complete even under high load. Page 5
Sheet2 This probably makes it impractical to limit low priority requests, which may routinely take very long times to complete.
ecuted with the priorities normal and low.
processes are a critical system resource.
Sheet3 Session Type System SAP GUI Sync. RFC Async. RFC RFC UI HTTP HTTP UI Batch SMTP BGRFC Scheduler BGRFC Unit
Priority High High Normal Normal High Normal High Low Normal High Normal
1962145 - Dynamic work process starts and stop frequently RSPARAM report You can set this parameter to 0 if u dont want your dialog process to get timeout
Sheet3 Description Internal session (e.g. to execute Auto-ABAP or other internal tasks) Online session with SAP GUI front end Synchronous RFC server session Asynchronous RFC server session Online RFC server session (e.g. SM51 - remote logon) HTTP session Online session with HTTP UI Session with background processing SMTP (Simple Mail Transfer Protocol) session Background RFC scheduler session Background RFC unit
cess starts and stop frequently 0 if u dont want your dialog process to get timeout
Sheet3 Parameter rdisp/scheduler/prio_low/max_quota rdisp/scheduler/prio_normal/max_quota
Default 80% 80%
Parameter rdisp/scheduler/prio_low/max_runtime rdisp/scheduler/prio_normal/max_runtime rdisp/scheduler/prio_high/max_runtime
Default (empty) 60m 10m
Sheet3 Description low prioorrequests Maximum quota of work processes used for normal low prio requests Description Maximum run time for low prio requests Maximum run time for normal prio requests Maximum run time for high prio requests
rdisp/scheduler/ prio_normal/max_runtime This parameter limits the time for which a request with normal priority can run uninterrupted in a dialog work process before it Interruptions, that is, activities that could lead to a work process switch (roll-out) (for example, COMMIT WORK, RFC call, and For reasons of backward compatibility, this parameter only takes effect, if the parameter rdisp/max_wprun_time is not explicitly The rdisp/scheduler/prio_*/max_runtime parameters provide the same functionality as the parameter rdisp/max_wprun_time, b The system assigns normal priority to all RFC and HTTP dialog requests that are not directly triggered by user interaction. The intention behind this parameter is mainly defensive. It limits the consequences of an activity unintentionally running for a l it means that a hanging request or a programming error cannot indefinitely block a dialog work process that is intended for act Choose a value that allows enough time for correctly-running requests with normal priority 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 pe The unit can be specified as seconds, minutes, hours, or days by adding ‘s’, ‘m’, or ‘h’ . There can be spaces between the valu Specifications without a unit are interpreted as seconds. If not value is specified, the runtime is unlimited.
rdisp/scheduler/prio_high/max_runtime This parameter limits the time for which a high-priority request can run uninterrupted in a dialog work process before it is force The system assigns high priority to all dialog requests that are directly triggered by user interaction (GUI, RFC remote logon th
rdisp/scheduler/prio_low/max_runtime This parameter limits the time for which a low-priority request can run uninterrupted in a dialog work process before it is forced The system assigns low priority to all RFC dialog requests that are triggered by a background request.