Scripting Guide - SAS

Chapter 4 Scripting Tools 61
Debug Scripts
Delete a Condition
On the Breakpoints tab, click in the breakpoint’s Condition field and press DELETE.
Specify Break Options
Right-clicking the breakpoint and selecting Edit Breakpoint provides a quick way to manage breakpoint
behavior. Alternatively, select the breakpoint on the Breakpoints tab and click . Both methods display
the Breakpoint Information window, where you customize settings on the Hit Count and Action tabs.
Change the Hit Count
You can control the number of times a breakpoint must be hit and when the break occurs. For example, to
break when the condition is met twice, select break when the hit count is equal to and type 2 on the Hit
Count tab.
Define an Action
You also have the option of defining a JSL expression or script that the Debugger executes when a
breakpoint is hit and execution has stopped. This script is called an action. On the Action tab, enter the JSL
expression to be executed.
Run the Script to the Cursor
When you right-click and select Run To Cursor, all expressions before the location of the cursor are
executed. Select this option when you only want to see values up to the current line. To see values when each
expression is executed, use the stepping options.
Tips for Setting Breakpoints
• If you do not want to watch for errors in a specific loop, set a breakpoint after the loop ends. The
Debugger will hit the next breakpoint rather than stepping through each line of the loop.
• Avoid inserting a breakpoint in lines that do not trigger an action (such as comments, blank lines, and
end parentheses). Debugger will not break on these lines.
• When you insert breakpoints, close Debugger, and edit the script, the breakpoints remain on the
original line numbers. You might need to delete and then reinsert the breakpoints.
• Breakpoints are remembered across Debugger sessions. This means that your breakpoints list includes
breakpoints that have been set in all scripts, not just the script that you are currently debugging.
• Breakpoints are remembered by the Debugger session, not by each script. This means that breakpoints
are listed even for scripts that have been moved or deleted.
• On the Breakpoints tab, click to remove all breakpoints in scripts whether they are currently open
or not, or for scripts that no longer exist.