Starting and Exiting

1. Checking the Debugger Settings

Before you start the ABAP Debugger, you can check the Debugger settings and, if necessary, adapt them to suit your requirements. To do this, choose the following menu in the ABAP development environment - for example, in the ABAP Editor (transaction SE38) or in the Object Navigator (transaction SE80):  Utilities  Settings  ABAP Editor  Debugging .

2. Starting the ABAP Debugger

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

3. Exiting the 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. Setting the Debugger Waiting Time

The time for which the new Debugger is active is limited 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 functions  Change  Change Value .