Show TOC

Procedure documentationStarting and Canceling Locate this document in the navigation structure

Procedure

  1. Selecting the Debugger

  2. Starting the New ABAP Debugger

  3. Canceling the New ABAP Debugger

  4. Switching Between the Classic and the New ABAP Debugger

  5. Setting the Debugger Waiting Time

1. Selecting the Debugger

Before starting the Debugger, the user must decide whether he wants to work with the classic or the new Debugger. To do this, the user must choose the required Debugger type in the ABAP development environment – for example, in the ABAP Editor (transaction SE38) or in the Object Navigator (transaction SE80) under the path   Utilities   Settings   ABAP Editor   Debugging  .

2. Starting the New ABAP Debugger

You start the new ABAP Debugger by calling or terminating the ABAP program to be tested in a specific way. For more information, see Starting the New ABAP Debugger.

3. Canceling the New ABAP Debugger

You can have the following different situations:

  • The Debugger is ready for input and the application is waiting for input. In this case, the path   Debugger   Exit Debugger   needs to have been run through. This way the Debugger is closed and the application continues to run. If the Debugger and the application are to be exited at the same time, then you must choose the menu path   Debugger   Exit Application and Debugger  .

  • The application is ready for input and the Debugger is waiting for input. In this case, the Debugger attached to this mode is closed using the function code /hx.

4. Switching Between the Classic and the New Debugger

It is possible to switch between the classic and the new Debugger at any time. In this case, all the breakpoints for both Debuggers remain visible.

  • To switch from the classic Debugger to the new Debugger, you must go through the path   Debugger   Switch to New ABAP Debugger  .

  • To switch from the new Debugger to the classic Debugger, you must go through the path   Debugger   Switch to Classic ABAP Debugger  .

When you switch from the new Debugger to the classic Debugger, the system may reach ABAP code which the classic Debugger cannot edit. This is ABAP code that is called directly from the kernel of the Web application server. This concerns primarily conversion and field exits. If these kinds of modules are analyzed using the new Debugger, the runtime error RPERF_ILLEGAL_STATEMENT is triggered whenever you change to the classic Debugger.

5. Setting the Debugger Waiting Time

The time for which the new Debugger is active is determined by the profile parameter rdisp/max_debug_lazy_time – which is set to 600 seconds in the standard version. After this time space has elapsed, the Debugger process is exited automatically and control is passed back to the application. Using transaction RZ11, the system administrator can change the value of this parameter by calling the function   Change   Change Value  .