Selecting Window > Preferences from the workbench menu bar opens the Preferences dialog box. Stored procedure debug settings specified in this dialog box do not take effect until the start of the next session. In the dialog box, choose Run/Debug > DB2 Stored Procedure Debugger to access the following preferences that you can set for debugging procedures:
Preference | Explanation |
---|---|
Number of seconds of inactivity before the procedure runs to completion | If you stop debugging an SQL stored procedure
for the length of time specified in this field, the debug session
will terminate and the procedure will run to completion. The minimum
value of this setting is 30 seconds and the maximum value is 1800
seconds. The default value of this setting is 300 seconds. Note: This
setting does not apply when debugging Java™ stored
procedures.
|
Maximum number of characters reported in large variables | This setting controls the maximum number of
characters that are displayed for the value of variables in the Variables view.
The default value of this setting is 80 characters. Note: This setting
does not apply when debugging Java stored
procedures.
|
Number of characters per line in Variables View Details Pane | This controls the position at which characters
will wrap in the Details Pane in the Variables view.
Each line of the Details Pane will have the number of characters specified
and then wrap to the next line. The default value of this setting
is 72 characters. Note: This setting does not apply when debugging Java stored procedures.
|
Diagnostic error trace level on DB2 server | This determines the level of error tracing on
the DB2 server. Valid entries in this field are:
|
DB2 Routine Debug Session Manager Location section | The
session manager connects the debugger user interface to the DB2 server
and must be running before the debug session can start. In this preference
section, you can choose to use a session manager on the server the
stored procedure is being run on or use an existing session manager.
A standalone session manager can be used when the DB2 server that you are debugging does not have a session manager available. To start a standalone session manager, run the db2dbgm batch file under the install directory for this product (there are two different batch files: db2dbgm.bat is for Windows® and db2dbgm is for Linux®). You can modify the batch file to specify a different port value if the default value is not available. You must start the standalone session manager before you try to use it with this product and you must specify in the stored procedure debug preferences that you are using a standalone session manager. To do this, open the DB2 Stored Procedure Debugger preference page, select the Use already running session manager radio button, and complete the Host and Port fields as described above. |
Do not use TCP/IP socket to communicate with debug session manager | For database servers that support it, the debugger will automatically use a TCP/IP socket to communicate with the session manager to improve debugger performance. If you do not want to use a socket (for example, you may not want to use a socket with a firewall), check this option. |