Parameter
abap/rabax_no_debug
Short text
Disallow debugging if a short dump occurs.
Parameter Description
If a runtime error occurs, the initial screen of the dump display appears.
If the user has debug authorization, he or she can analyze the error in the debugger. To do so, the the data used by the application at the time of the crash must be retained unchanged.
If multiple memory-intensive applications terminate within a short space of time, and then remain on the initial screen of the dump display for a longer period of time, this can lead to memory bottlenecks.
If the profile parameter is set, all application sessions are terminated and therefore the memory used is released, before the initial screen is displayed. This avoids the impending threat of bottlenecks. However, in this case, it is no longer possible to debug the terminated application.
The parameter can have one of the following values:
‘on’ the parameter is active and is suppressing the possibility of debugging. The occupied memory areas are released.
‘off’ the parameter is inactive. If the user has debug authorization, he or she can analyze the error in the debugger. Occupied memory areas are retained.
If the user does not have debug authorization, the occupied memory may be released before the dump display is output, depending on the kernel status (see SAP Note 1500931).
Application Area
ABAP
Parameter Unit
–
Default Value
off
Who is permitted to make changes?
System administrator
Operating System Restrictions
None
Database System Restrictions
None
Are other parameters affected or dependent?
No
Values allowed
See above
