Programming Guide : Debugging Your Application : How You Can Use Break Conditions : Error Break Conditions
 
Share this page          
Error Break Conditions
An error break condition passes control to the Debugger when the error break that you set occurs. You can set an error break condition for any of the following error types:
All errors
DBMS errors
Data facility errors that result from such situations as data type mismatches
Communication errors that originate from the General Communication Facility (GCF)
Specific error class or error number
The OpenROAD Debugger gains control at an indeterminate point in the execution of the statement that caused the error. After you return control to the application, error handling occurs as it would in a runtime environment. That is, the application handles the error as if you had not intercepted the error with the Debugger. In some cases, this behavior can take you to the end of the event block.
Set Error Break Conditions
You can set error break conditions in the Breakpoints: Events, Errors and Threads portlet (Other portlet tab) of the Debug tab.
To set error break conditions
1. Click the Develop tab and select the application in which you want to set error break conditions in the Applications portlet.
2. Click the Debug tab.
3. Click the Other portlet tab on the right side of the Workbench window.
The Breakpoints: Events, Errors and Threads portlet is displayed.
4. In the Error Break Conditions section, select one or more types of errors that you want to set as break conditions, or check All Errors to set break conditions for all error types.
Error break conditions are displayed in the Activations pane of the Current Break Conditions for Application window. If you want to deactivate or reactivate a break condition, select or clear the appropriate check box in the Activations portlet.
To set an error break condition for a specific class of error or a specific error number
1. Click the Develop tab and select the application in which you want to set event break conditions in the Applications portlet.
2. Click the Debug tab.
3. Click the Other portlet tab on the right side of the Workbench window.
The Breakpoints: Events, Errors and Threads portlet is displayed.
4. In the Error Break Conditions section, select the Specific Error option.
5. Select the desired class from the Class drop-down list.
6. (Optional.) Specify a specific error number within the class: in the Number entry field, type the number in hexadecimal format.
Note:  The hexadecimal form of the error number is the four-digit number that appears directly after the facility code in Ingres error numbers. For example, if the error number is E_US0041, the hexadecimal number that you would enter is 0041.
OpenROAD validates your error class and number entries, and alerts you if the class you specified does not exist or if your number is not a valid hexadecimal number.
The specific error break condition is displayed in the Activations portlet of the Debug tab. If you want to deactivate or reactivate a break condition, select or clear the appropriate check box in the Activations portlet.