Error Handling

1. Error During a Debugging Session

If an error should actually occur in user interface processing while the Debugger is running, the user interface is restarted automatically. In this case, a window is displayed where you can delete settings already made. The system then performs a restart with the standard layout. Alternatively, it is possible to switch to the classic Debugger in the same window.

This restart only affects the interface, but not the application to be analyzed. Therefore, all settings and breakpoints remain intact and you can continue debugging at the same point in the program.

If there is an error, the log file TPDA_ERROR is written to the home directory DIR_HOME in the current application server. This can then be analyzed and deleted using the report RSTPDAADMIN_TRACE. Incorrect layout variants can be deleted using the report RSTPDAADMIN.

2. Error When Starting a Debugging Session

If errors occur when you initialize the new Debugger, for example, due to non-existing tools, a window is displayed with the following options:

• Switch to the classic Debugger

• Exit the current Debugger session

• Restart the Debugger using the standard layout

In addition, an error text is issued in the status line of the window displayed. This describes the type of error that has occurred.