BASIS Parameter rdisp/max_wprun_time

Hi,
Does anybody knows how the time limit given in the profile parameter rdisp/max_wprun_time work?
I mean our parameter is set to 3600. What does that mean? Does it mean that it will kill dialog process at 3600 secs or 7200 secs?
Today our system almost came down as there were bex users (mostly with killed excel programs) which still had a process in SAP running for more than 40000 secs. Any idea why the parameter didnt work?
Also if the parameter gives two times its value before the dialog work process is killed why today I saw one dialog process getting killed at 3600 secs in sm66 shouldnt it get killed after 7200 seconds.
I though the parameter is defined such that if rdisp/max_wprun_time=n then maximum dialog process runtime would be 2n and after n seconds smm66/sm51 would show up as red and after 2n it would be cancelled altogether...
please help

Hallo BWNovice
The parameter is giving you maximum time for Dialog Process - for example when you run a bex query. The default is 600 sec but yo0u can extend as much as you want I suppose. But be carefully because then you can have process which run for 6000-7000 thousand seconds which can affect macvhine performance (depend on your machine). Usually 3600 is a good time, thinking also for the loading during the night where you can have some dialog processes which takes some time.
Regarding your question: if you have it set-up 3600 and you run a bex report which takes more than 3600 at 3600 then the process will be killed by the system.
But a suggestion: you should avoid to have process which run so long time in your machine, specially bex report.
I hope this can help you.
Mike

Similar Messages

Runtime parameter rdisp/max_wprun_time is set to 1700

u201CCaller 70u201D missing error. This is happening because the runtime parameter rdisp/max_wprun_time is set to 1700. If I edit it to 15000 temporarily and re run the load, the load is successful.
this is popping up at the point of updating data targets, in the 1st set of data package while the second loads successfully.
Krishna.

The runtime parameter rdisp/max_wprun_time defines the time limit for a foreground process. While backgound processes are permitted to run with out any limit. With this parameter the foreground/dialog processes are permitted to run for the defined amount of time, beyond this the system will cancel them terming it as time limit exceeded error.
The standard defined by SAP for this parameter is 3600, but depending on our business need we can increase or decrease this value. Usually taken care by Basis Administrators.
Regards,
Habeeb

Determine/read the value of parameter rdisp/max_wprun_time within ABAP

Hi,
I need to avoid program breaks caused by exceeding run time longer than defined in parameter rdisp/max_wprun_time.
I will check the time since start of report in the critcal loop to bring the current data changes to a controlled end before getting a program break. I won't put a constant to the report, I will have a dynamical routine to avoid changes of report if the value of parameter rdisp/max_wprun_time will be changed.
But how can I get the value of this parameter within my ABAP report? Is there a table where this value has been stored? Is there an existing function module or a method to read the value?
Thank's a lot in advance!
Georg

The runtime parameter (GET RUN TIME ) can be used to dynamically get the program run time
DATA T TYPE I.
GET RUN TIME FIELD T.
WRITE: / 'Runtime', T.
or
U probably can store the start date and time in TVARV with some variable ( line concatenate program name + START Date + Time)
and then use
SD_DATETIME_DIFFERENCE
or
SD_CALC_DURATION_FROM_DATETIME
Regards,
Mithun Shetty

The system profile parameter rdisp/max_wprun_time how to cinfigure this in ecc system

Hi,
Can any body tell me the procedure how can we configure the the system profile
parameter rdisp/max_wprun_time in ecc system step by step procedure
Regards
Madhu

Hi Madhu,
If we change the max parametere here my be our problem will solved right.
See this link is usefully
http://scn.sap.com/thread/2045008
Adding some comment to that rz-10 is different than RZ10?
There is no t-code like rz-10.
rz10 is the t-code for profile parameters
Regards,
Deva

Changing rdisp/max_wprun_time

I have a third party program which uses a back ground account to connect to SAP and run ABAP. This ABAP program is taking longer than 5 minutes and it is timing out with error:
SR_17009 Error in CPIC: [CMRCV: 18 Time limit exceeded
Current I am using SAP R3 4.x and will be moving to SAP ECC 6.x in future.
I have read that one can change following parameter
rdsip/rdisp/max_wprun_time to change the default time.
I have following questions, some of them are naive:
1. Does a background account(my third party cannot login interactively) still use Dialog Processes.
2. I am assuming I have to create s special profile for setting this parameter so it does not affect other accounts. What command do you use to create this profile.
3. What command do I use to assign my third party account to this profile.
4. How do I found which account has which profile.
THANSK A LOT.

Zigzagdna,
The parameter rdisp/max_wprun_time is not user or profile specific. It affects the entire system. Simply defined, it defines the amount of time a dialog work process can be occupied by one step (can be seen in SM50). Which user you use to run/call the ABAP program, does not change or decide the time.
1. Does a background account(my third party cannot login interactively) still use Dialog Processes.
Yes, it can. Most program need both dialog work processes and background.
2. I am assuming I have to create s special profile for setting this parameter so it does not affect other accounts. What command do you use to create this profile.
No, you dont need a profile.You can change this value from the Tcode RZ11.It can be changed and the new value is taken into effect without restarting the SAP system (dynamically switchable).
3. What command do I use to assign my third party account to this profile.
Not applicable
4. How do I found which account has which profile.
Not applicable
I dont have the exact info of your program, but from what it sound like, it could be timing out because of RFC timeout. If it is not running from the SAP Gui, it must make RFC calls to the server.
Kunal

Win8.1 Pro & Flash Player 11.9.900.117 "base" parameter issue

While "streamlining" some code for a web site, I just discovered that my solution doesn't work on my 2 Win8.1 PCs, but works in Vista 32-bit and Win7 64-bit machines. I've tested it in IE, Firefox and Chrome. (By "doesn't work", I mean I get an empty block where the Flash Player frame is supposed to be. Right-clicking on the area brings up the Flash settings menu.)
The change I made was to have all web pages in the "root" directory of the web site, and the videos (.swf and .flv files) in the "video" directory. Previously, the web pages that ran the videos were in the "video" directory. (This still works on the Win8.1 PCs.) I added the "base" parameter to the code (shown below) to direct the Flash Player to the "video" directory.
I've been poring through the Adobe site and various forums (fora ?) looking for a clue, but came up empty. Can anyone shed some light on the issue?
If you want to see the site, goto http://theolivebranchforchildren.org to see the current version,
and go to http://theolivebranchforchildren.org/index.php to see my revamped version.
Go to the Gallery page and click on any of the video links in the sidebar. (The example shown below is for the "Aids Testing" option [aids.flv video file].)
This is the code (as copied from the "view Source" option of the browsers - all identical) that runs in Vista and Win7 but not in Win8.1 ...
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,0,0" width="502" height="322" id="FLVPlayer">
<param name="base" value="video" />
<param name="movie" value="video/FLVPlayer_Progressive.swf" />
<param name="salign" value="lt" />
<param name="quality" value="high" />
<param name="scale" value="noscale" />
<param name="FlashVars" value="&MM_ComponentVersion=1&base=video&skinName=Halo_Skin_3&streamName=aids&autoPlay=true&autoRewind=false" />
<embed src="video/FLVPlayer_Progressive.swf"
flashvars="&MM_ComponentVersion=1&base=video&skinName=Halo_Skin_3&streamName=aids&autoPlay=true&autoRewind=false"
quality="high" scale="noscale" width="502" height="322" name="FLVPlayer" salign="LT"
type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" />
</object>
FOLLOW-UP 10/21/2013 -- I almost got around the problem by creating soft links in the web site's root directory to the files in the video directory. This is an ugly workaround, but suggests that the "base" parameter is being totally ignored in the Win8.1 implementation of Flash Player by Firefox & Chrome, both of which can now play the videos. It still doesn't work in IE11, though.
... AL
Please visit http://www.theolivebranchforchildren.org/ to see a miracle developing.

The "base" parameter issue, as I described it above, has "gone away" silently. Now I can play the movies via Flash Player in IE11, FireFox, Chrome and Safari on my two Win8.1pro laptops. IE11 was the last holdout -- I had to turn off the PopUp Disabler in the IE settings to let the Flash Player play.
I'm a happy camper now.
... AL

Msprot: cant read profile parameter rdisp/mshost

Hi
When I run : msprot -name <SID> -l it returns:
cant read profile parameter rdisp/mshost
rdisp/mshost is set in the default profile to : sapms<SID>
in etc/services sapms<SID> is assigined to <port_number>/tcp
If you change rdisp/mshost to the port number rather than sapms<SID> it works....but we don't want to change the parameter to the port number.
Thanks
Jim

Thanks.....i've being testing the command....it's like it can't read the default profile...
if i use mshost switch it complain it can't read msserv.....once I use both switch it runs ok....
I changed default profile to 777 just to test if it was a permissions issue but that didn't make a difference.
Thanks for the note but that seems to be dealing with windows...i'm working on sun...tried it on linux also and get
the same problem....
Cheers
Jim

Is the parameter : rdisp/bctime in the instance profile?

Is the parameter:rdisp/btctime in instance profile? I can not find it in the instance profile. if it is not writed in the instnace profile, is the default value 60 seconds?
thanks
Edited by: victor on Sep 10, 2008 4:30 AM

Hi Victor,
not all parameters you will find in the instance profile.Some default ones and maintained ones can be seen.if it is not there you can manually add it in t-code rz10.
Have a look at below link
http://help.sap.com/erp2005_ehp_03/helpdata/EN/c4/3a6247505211d189550000e829fbbd/frameset.htm
Regards
Ashok

Setting Profile parameter rdisp/gui_auto_logout value

Hi All,
The present value for the profile parameter value rdisp/gui_auto_logout is 1200 sec, now i would like to change the value from 1200 sec to 2400 sec.
can change the value directly in parameter value field (using T-code RZ10) or can i create a new parameter value?
Please any one give me the suggestions how to reset the value for this profile parameter
Regards,
Reddy V,

Hello reddy,
This rdisp/gui_auto_logout parameter can be changed dynamically too you can change the value via RZ11 if you dont want to restart your server now. but in this case whenever you will restart your server the parameter value will be set back to the original state
change it via RZ10 but in this case you have to start the server to activate this value
Select Change in instance profile via RZ10 and select extended maintainance then click on create parameter and enter the parameter name there and press enter, it will show you the current value then insert the new value and save and activate the profile.
Regards
Subhash

Are there any troubles with high rdisp/max_wprun_time?

Are there any unpredictable negative effects while setting this parameter large values (for example, 1000 or 2000 seconds?)

Hi Pavel Danilov,
You can increase the value but this increases the chance of work processes being blocked (eventual system standstill situations possible). I assume you have reviewed note <a href="http://service.sap.com/sap/support/notes/25528">25528</a> and other documentation about this parameter. There can be some reasons why 600 is not high enough also for current needs..
Normally if you have very long running database accesses, than this indicates that the program is in a loop or no suitable index exist for this access so that a full table scan is performed or the optimizer has a problem with the statement.
You can check as well if the reason for the long running task is:
- Overload of the SAP System and/or of the database
- Waiting for locks in the DB
Regards, Mark

Program terminated: Time limit exceeded, ABAP performance, max_wprun_time

Hi,
I am running an ABAP program, and I get the following short dump:
Time limit exceeded. The program has exceeded the maximum permitted runtime and has therefore been terminated. After a certain time, the program terminates to free the work processfor other users who are waiting. This is to stop work processes being blocked for too long by
- Endless loops (DO, WHILE, ...),
- Database acceses with large result sets,
- Database accesses without an apporpriate index (full table scan)
- database accesses producing an excessively large result set,
The maximum runtime of a program is set by the profile parameter "rdisp/max_wprun_time". The current setting is 10000 seconds. After this, the system gives the program a second chance. During the first half (>= 10000 seconds), a call that is blocking the work process (such as a long-running SQLstatement) can occur. While the statement is being processed, the database layer will not allow it to be interrupted. However, to stop the program terminating immediately after the statement has been successfully processed, the system gives it another 10000 seconds. Hence the maximum runtime of a program is at least twice the value of the system profile parameter "rdisp/max_wprun_time".
Last error logged in SAP kernel
Component............ "NI (network interface)"
Place................ "SAP-Dispatcher ok1a11cs_P06_00 on host ok1a11e0"
Version.............. 34
Error code........... "-6"
Error text........... "connection to partner broken"
Description.......... "NiPRead"
System call.......... "recv"
Module............... "niuxi.c"
Line................. 1186
Long-running programs should be started as background jobs. If this is not possible, you can increase the value of the system profile parameter "rdisp/max_wprun_time".
Program cannot be started as a background job. We have now identified two options to solve the problem:
- Increase the value of the system profile parameter "rdisp/max_wprun_time"
- Improve the performance of the following SELECT statement in the program:
SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
INTO CORRESPONDING FIELDS OF TABLE i_ekkn
FOR ALL ENTRIES IN p_lt_proj
WHERE ps_psp_pnr = p_lt_proj-pspnr
AND ps_psp_pnr > 0.
In EKKN we have 200 000 entries.
Is there any other options we could try?
Regards,
Jarmo

Thanks for your help, this problem seems to be quite challenging...
In EKKN we have 200 000 entries. 199 999 entries have value of 00000000 in column ps_psp_pnr, and only one has a value which identifies a WBS element.
I believe the problem is that there isn't any WBS element in PRPS which has the value of 00000000. I guess that is the reason why EKKN is read sequantially.
I also tried this one, but it doesn't help at all. Before the SELECT statement is executed, there are 594 entries in internal table p_lt_proj_sel:
DATA p_lt_proj_sel LIKE p_lt_proj OCCURS 0 WITH HEADER LINE.
p_lt_proj_sel[] = p_lt_proj[].
DELETE p_lt_proj_sel WHERE pspnr = 0.
SORT p_lt_proj_sel by pspnr.
SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
INTO CORRESPONDING FIELDS OF TABLE i_ekkn
FOR ALL ENTRIES IN p_lt_proj_sel
WHERE ps_psp_pnr = p_lt_proj_sel-pspnr.
I also checked that the index P in EKKN is active.
Can I somehow force the optimizer to use the index?
Regards,
Jarmo

Do we have any parameter to limit the runtime of the HTML services like BEx

Dear all,
In one of our BI production system few RFC usersu2019 lunches BEX WEB analyzer using html service and they are leaving their sessions for ever, which in turn causes Obsolete lock entries in SM12.
I know that we have parameter (rdisp/max_wprun_time) to limit the dialog work process run time.
Do we have any parameter to limit the runtime of the HTML services like BEx WeB. Please suggest me how to Limit RFC users runtime.
Thanks
--Murali

you can use an ICM timeout - but then this will also affect long running queries if you set it too low.
icm timeout is a system parameter and not specific to your query alone.
Otherwise you can have a portal and setup DSM ( Distributed Session Management) to handle the same...
Sorry it was ICM timeout... and not ICF...
http://www.saptechies.com/icm-and-sap-web-dispatcher-timeout-parameter/&ei=PXnvSaaYDJOdlQeBqo3CBw&usg=AFQjCNGict0Qj7n2if1qcvr6M6S6D1R6mA
Edited by: Arun Varadarajan on Apr 23, 2009 1:38 AM

Dialog WP runtime exceeds value set in rdisp/wp_max_runtime

Dialog wp runtime exceeds the value set in parameter rdisp/wp_max_runtime
Value set for rdisp/wp_max_runtime is 1500 but wp runtime exceeds more than 10,000. we are using 4.5B system on Oracle/AIX.
Please suggest how to avoid such wp running for more than value set in parameter rdisp/wp_max_runtime.

Hi Rudra,
rdisp/max_wprun_time essentially may not stop the process all th time especially if your work process is waiting for some information or waiting for some query to execute.
Read the following note which describes the behaviour of this parameter
Note 25528 - Parameter rdisp/max_wprun_time
Hope that helps.
Regards,
Siddhesh

Maximum Time Exceed.

Hi Guru's,
I executed the MB5B report for finding the opening and closing stock providing the Material, Plant, Company code, Posting date but it took long execution time and ended in 'Maximum Time Exceed'.. I also tried in Background but the job didnt collected in spool, the spool list is empty. Before a week the report ran fine.. even i checked for a particular date..Please give me a solution.
Thanks,
Satish.M.R

Dear,
Check note: Note 25528 - Parameter rdisp/max_wprun_time and also consult your BASIS team.
Regards,
Syed Hussain.

Timeout dumps

Hi All,
In our PI Production system we are getting lot of time out dumps in ST22 as below.
The program u201CCL_XMS_PERSIST_ADM============CPu201D has exceeded the maximum permitted uninterrupted runtime and has therefore been terminated.
I have checked all of Dialog work process is Running and ON HOLD state is it any cause for these dumps.. as well as rdisp/max_wprun_time chaged to 900.
Short text
    Time limit exceeded.
What happened?
    The program "CL_XMS_PERSIST_ADM============CP" has exceeded the maximum
     permitted uninterrrupted
    runtime and has therefore been terminated.
What can you do?
    Take note of the actions and inputs that lead to the error.
    Contact your SAP administrator for further processing of the problem.
    Using transaction ST22 for ABAP short dump analysis you can see and
    administrate termination messages and retain them for a longer period.
Error analysis
    The system profile contains the maximum runtime of a program.
    When this time limit has been exceeded, the program is terminated
    to make way for other users who may be waiting.
    In the case of a work area, this means that
    - endless loops (DO, WHILE, ...),
    - database accesses producing an excessively large result set,
    - database accesses without a suitable index (full table scan)
    do not block the processing for too long.
Kindly advice on this..
Regards,
KUMAR

i am able to view the messages in SXMB_MONI but when i click on message to open it will taking long time then it creates dump..
pls find logs below
How to correct the error
    Long running programs should generally be run as batch jobs.
    If that is not possible, the system profile parameter "rdisp/max_wprun_time"
     can be
    enlarged.
    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
      Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
      (for example);
    - Database has unsuitable index: Check index generation.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    please use the following search criteria:
        "TIME_OUT" " "
        "CL_XMS_PERSIST================CP" bzw.
     "CL_XMS_PERSIST================CM02M"
        "READ_CHILDS"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem (short dump).
       To obtain this, select "System->List->Save->Local File (unconverted)"
       on the current screen.
    2. A suitable hardcopy printout of the system log.
       To obtain this, call the system log with Transaction SM21
       and set the time interval to 10 minutes before and 5 minutes after
       the short dump. In the display choose "System->List->Save->
       Local File (unconverted)"
    3. If the programs are your own programs or modified SAP programs,
======================================================================================
Tue Jan 4 17:26:46 2011
rdisp/max_wprun_time: 900 -> 1200
Tue Jan 4 17:59:30 2011
rdisp/max_wprun_time: 1200 -> 1800
Tue Jan 4 18:31:50 2011
     OCIStmtExecute() failed with -1=OCI_ERROR
     SQL error 1013:
SQL cancelled; calling registered function at 4efd80
program canceled
    reason   = max run time exceeded
    user     = PISUPER
    client   = 500
    terminal = dv2700-PC
    report   = CL_XMS_PERSIST================CP
TH VERBOSE LEVEL FULL
RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
RABAX: level LEV_RX_SAVE_SHMLOCKS entered.
RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
RABAX: level LEV_RX_RESET_SHMLOCKS entered.
RABAX: level LEV_RX_RESET_SHMLOCKS completed.
RABAX: level LEV_RX_ROLLBACK entered.
RABAX: level LEV_RX_ROLLBACK completed.
ABAP Program CL_XMS_PERSIST================CP        .
Source CL_XMS_PERSIST================CM02M      Line 53.
Error Code TIME_OUT.
Module $Id: //bas/710_REL/src/krn/th/thhiserv.c#12 $ SAP.
Function ThTimeout Line 1736.
RABAX: level LEV_RX_STDERR completed.
RABAX: level LEV_RX_RFC_ERROR entered.
RABAX: level LEV_RX_RFC_ERROR completed.
RABAX: level LEV_RX_RFC_CLOSE entered.
RABAX: level LEV_RX_RFC_CLOSE completed.
RABAX: level LEV_RX_IMC_ERROR entered.
RABAX: level LEV_RX_IMC_ERROR completed.
RABAX: level LEV_RX_DATASET_CLOSE entered.
RABAX: level LEV_RX_DATASET_CLOSE completed.
RABAX: level LEV_RX_ERROR_SAVE entered.
RABAX: level LEV_RX_ERROR_SAVE completed.
RABAX: level LEV_RX_ERROR_TPDA entered.
RABAX: level LEV_RX_ERROR_TPDA completed.
RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
RABAX: level LEV_RX_END entered.
RABAX: level LEV_RX_END completed.
RABAX: end no http/smtp
RABAX: end RX_GOTO_RABAX
Time limit exceeded..
regards,
kumar

BASIS Parameter rdisp/max_wprun_time

Similar Messages

Maybe you are looking for