Transfer Control to the Operating System Debugger
escapecommand transfers control from the SAS/C Debugger to TEST under TSO or to CP under CMS and lets you return to the program executing under the SAS/C Debugger at the place where you left it. You enter TEST or CP in the context of the program being debugged. You need to perform the following steps before you can use
When you issue the
command while executing your program under the SAS/C
Debugger, you escape to TSO TEST or CP. The screen is refreshed after completion
of execution of the
If you do not request the breakpoint for
escape according to the
instructions and try to use
escape, nothing happens. The debugger cannot check whether
you requested the breakpoint.
In addition, you do not need to request the breakpoint
immediately on entry to the debugger. You can note the address and use it
later to request the breakpoint when you want to use
escape, you must run the SAS/C Debugger under TSO TEST.
CMS: When you are running the SAS/C Debugger
under CMS, use the debugger command
to issue a PER command to request a breakpoint. (Under VM/XA, the TRACE command
is used instead of PER.) For example, if the breakpoint that you want to request
is at 00D174, the following command requests the breakpoint:
system CP PER I R D174
Then, you can use
to leave the SAS/C Debugger, examine
your program under CP PER, and return to the SAS/C Debugger
via the CP command BEGIN. See the IBM publication CP Command and Utility
Reference SC24-5773 for more information about CP.
Register values: TSO and CMS: When
escape to give control to TEST or PER,
the register contents are the same as when the program transfers control to
Modifying register contents while escaped under TEST or PER may not work and could potentially cause 0CX or other undesired effects. See return for information about setting RETURN values.
|Source window prefix||none|
escapecommand is not affected by changes in scope.
Top of Page
Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.