Start of Content Area

Procedure documentation    Error Handling

 

1. Error during a Debugger session
2. Error when starting the Debugger session

 

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. For this reason, all the settings and breakpoints are kept and you can continue with the debugging process at the same place.

If there is an error, the log file TPDA_ERRORis written to the home directory DIR_HOME of the current application server. You can analyze and delete this report using the report RSTPDAADMIN_TRACE. You can delete incorrect layout variants using the report RSTPDAADMIN.

 

2. Errors While Starting a Debugger Session

If errors occur already during initialization of the new Debugger – errors such as non-existent tools, for example, the system will display a window with the following options:

In addition, an error text will appear in the status line of the displayed window. This describes the type of error that occurred.

 

 

End of Content Area