Use the Debugger to debug any script that contains a procedure regardless of the SQL included in the script (i.e., SELECT statements).
Notes:
You can run the Debugger on a stored SQL procedure that has been compiled with the debug support code. When you launch the Debugger on a procedure, the procedure script opens in the Editor. From here, you monitor and control the debugging process.
To prepare and debug an SQL procedure
Select the Procedures node in the Database Explorer or Object Explorer.
Add the debug support code to the SQL procedure you want to debug. Use one of these methods:
» | Right-click the SQL procedure, and select Compile SQL Procedure with Debug. |
Note: For a DB2 for z/OS procedure, this method opens the Compile Subroutine window. To compile, complete the fields and execute the generated script. (The read-only Function field on the Build page shows REBUILD_DEBUG.)
Do one of the following.
Note: If errors occur during the compile process, Toad notifies you and rolls back the previous version of the procedure. If no errors occur, Toad commits the procedure.
Define the start parameters.
Tip: You can manually set start parameters at anytime during the debugging process by clicking in the Debug toolbar.
To... |
Use this Option Page... |
Set an option so function calls are not evaluated when hovering the cursor over watches |
Debugger | General |
Select a default desktop configuration that displays when starting or ending a debugging session | |
Set DB2-specific options, such as requirements for commits and debug-session time-outs |
Debugger | General | DB2 |
Tips:
If you have not set a breakpoint, clicking runs the SQL script to completion without stopping.
© ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center