Pressing Ctrl/C enables you to abort the execution of a debugger
    command or to interrupt program execution without interrupting
    the debugging session. This is useful when, for example, the
    program is executing an infinite loop that does not have a
    breakpoint, or you want to abort a debugger command that takes
    a long time to complete. The debugger prompt is then displayed,
    so that you can enter debugger commands.

    If your program already has a Ctrl/C AST service routine enabled,
    use the SET ABORT_KEY command to assign the debugger's abort
    function to another Ctrl-key sequence. Note, however, that many
    Ctrl-key sequences have predefined functions, and the SET ABORT_
    KEY command enables you to override such definitions (see the
    OpenVMS User's Manual). Some of the Ctrl-key characters not used
    by the operating system are G, K, N, and P.

    If your program does not have a Ctrl/C AST service routine
    enabled and you assign the debugger's abort function to another
    Ctrl-key sequence, then Ctrl/C behaves like Ctrl/Y-that is, it
    interrupts the debugging session and returns you to DCL level.

    Do not use Ctrl/Y from within a debugging session. Instead, use
    either Ctrl/C or an equivalent Ctrl-key sequence established with
    the SET ABORT_KEY command.

    You can use the SPAWN and ATTACH commands to leave and return to
    a debugging session without losing the debugging context.

                                   NOTE

       Pressing Ctrl/C to interrupt a program running under
       debugger control works only once. Thereafter, the Ctrl/C
       interrupt is ignored. The same is true when using the
       DECwindows STOP button; the action is acknowledged only
       the first time the button is pressed.

    Related commands:

       ATTACH
       Ctrl/Y
       (SET,SHOW) ABORT_KEY
       SPAWN