Hi Marius,
Thanks for your prompt reply. I went through the parameter info.
I understand that, in my case, the job which is apparently taking a long time to process in the foreground is being cut short by this "rdisp/max_wprun_time" parameter (and hence, the Time_out dump in ST22) to optimize the usage of the dialog processes and free them up. Considering that the parameter value cant be increased from the present limit, I believe the next fix is to convert this time-consuming program running in the foreground to a background process.
Can you please help me with the corrective actions (meaning Job name or report name etc) which need to be converted from a forground process to a Background process, and the exact way to do so. We are getting the exact same dump as in the heading of this thread.
The ST22 in our SP1 system contains only Time_out dumps (10 per day for that matter) and we're trying to fix it up. Appreciate your help. Thanks in advance.
Regards,
Mithun