Programming Guide - Actian

How You Can Use Break Conditions5. Select the desired class from the Class drop-down list.6. (Optional.) Specify a specific error number within the class: in the Numberentry field, type the number in hexadecimal format.Note: The hexadecimal form of the error number is the four-digit numberthat appears directly after the facility code in Ingres error numbers. Forexample, if the error number is E_US0041, the hexadecimal number thatyou would enter is 0041.OpenROAD validates your error class and number entries, and alerts you ifthe class you specified does not exist or if your number is not a validhexadecimal number.The specific error break condition is displayed in the Activations portlet of theDebug tab. If you want to deactivate or reactivate a break condition, select orclear the appropriate check box in the Activations portlet.Call Break ConditionsSet Call Break ConditionsA call break condition causes the application to give control to the OpenROADDebugger when the frame or procedure you specify is called. The Debuggertakes control just before the statement that calls the frame or procedure.Note: You cannot set a call break condition on a database procedure call.You can set call break conditions in the Breakpoints: Calls to components inapplication portlet (Calls portlet tab) of the Debug tab.To set a call break condition1. Click the Develop tab and select the application in which you want to setcall break conditions in the Applications portlet.2. Click the Debug tab.3. Click the Calls portlet tab on the right side of the Workbench window.The Breakpoints: Calls to components in application portlet is displayed,showing all of the called components in the application.4. Select the Break option for as many calls as desired.Call break conditions are displayed in the Activations portlet of the Debug tab.If you want to deactivate or reactivate a break condition, select or clear theappropriate check box in the Activations portlet.454 Programming Guide