Programming Guide - Actian

How You Can Use Break Conditions• Communication errors that originate from the General CommunicationFacility (GCF)• Specific error class or error numberSet Error Break ConditionsThe OpenROAD Debugger gains control at an indeterminate point in theexecution of the statement that caused the error. After you return control tothe application, error handling occurs as it would in a runtime environment.That is, the application handles the error as if you had not intercepted theerror with the Debugger. In some cases, this behavior can take you to the endof the event block.You can set error break conditions in the Breakpoints: Events, Errors andThreads portlet (Other portlet tab) of the Debug tab.To set error break conditions1. Click the Develop tab and select the application in which you want to seterror 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 errorsthat you want to set as break conditions, or check All Errors to set breakconditions for all error types.Error break conditions are displayed in the Activations pane of the CurrentBreak Conditions for Application window. If you want to deactivate orreactivate a break condition, select or clear the appropriate check box inthe Activations portlet.To set an error break condition for a specific class of error or a specificerror number1. Click the Develop tab and select the application in which you want to setevent 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.Debugging Your Application 453