Clearing Out Break Points

Chapter 4-5: The Debugger

To clear out hard-coded break points (TRAP statements), you can invoke the ILF editor and delete them. Alternatively, there are processes on the Utilities, Toolbox menu in Application Design that “Turn All TRAPs Off” and “Turn All TRAPs On” in a given application. The first process converts TRAP statements into “tftft TRAP” comments (where “tftft” is replaced by the actual T/F indicators if any are present on the TRAP statement) and the second process converts the comments back to TRAP statements. Remember that TRAP statements are not intercepted in the end user environment, so ordinary users will never be aware of their existence.

If TRAP statements are not deleted or turned off, they remain a permanent part of a routine. The break points that you set dynamically within the debugger by using select (F3) are automatically cleared when you leave the debugger. You must reactivate any dynamic break points when you return to the debugger.

APPX Application Design Manual (01/13/03)