Debug screen timeout

You have most likely noticed that whenever a session is left in debug mode for approximately ten minutes, the control returns to the "Easy Access Menu" with a message: "Transaction from DEBUG mode (after timeout) reset".

Since debugger holds a work processor permanently, it is not advisable to hold a work processor idle for more than ten minutes. Also if there are ten work processors, it is not advisable to allow ten people to hold ten work processors for debugging.

Following are the parameters that control the maximum holdtime of the workprocessor in debug mode:

rdisp/max_debug_lazy_time and rdisp/max_priv_time

Also, to stop ten people from debugging, use the parameter rdisp/wppriv_max_no. All the above parameters can be set by using the transactions RZ10/RZ11.

    Requires Free Membership to View

This was first published in March 2005

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.