Commands such as break, trace, and
on request actions
or breakpoints. Both breakpoints and actions cause an interruption in program
execution at a hook. However, after a breakpoint you must restart program
execution; by contrast, after an action, execution continues automatically.
When you request a breakpoint with break, for
example, you can then issue additional debugger commands (such as print, to print the value of a variable) and then restart
execution by using the go command.
In
addition to the argument that specifies where execution should be interrupted,
the break, on,
and trace commands can be used conditionally.
In this way, breakpoints or actions are requested when a special condition
is met. The WHEN clause is used to issue one of these commands conditionally.
See break, on, and
trace for
descriptions of the WHEN clause and how it is used.
Once you have requested several breakpoints, actions,
and monitors,
you may need to review a list of requests in effect. The query command lists the requests. Use the drop
command to drop requests that you no longer need, or use the ignore command to ignore requests temporarily at certain locations.
Also, with the disable command, you can deactivate
certain requests temporarily. Then you can use the enable
command to reactivate them.
Copyright © 2001
by SAS Institute Inc., Cary, NC, USA. All rights reserved.
