Reruns the program currently under debugger control.

                                   NOTE

       Requires that you started your debugging session with the
       DCL command DEBUG/KEEP and then executed the debugger RUN
       command. If you began your session with the DCL command RUN
       filespec instead, you cannot use the debugger RERUN command.

    Format

      RERUN

1  –  Qualifiers

1.1    /ARGUMENTS

       /ARGUMENTS="arg-list"

    Specifies a list of arguments. If you specify a quoted string,
    you might have to add quotation marks because the debugger strips
    them when parsing the string. If you do not specify arguments,
    any arguments that were specified previously when running or
    rerunning that program are applied, by default.

1.2    /HEAP_ANALYZER

    (Applies only to workstation users.) Invokes the Heap Analyzer, a
    debugger feature that helps you understand how memory is used
    by your application. For more information on using the Heap
    Analyzer, see the OpenVMS Debugger Manual.

1.3    /SAVE

       /SAVE (default)
       /NOSAVE

    Controls whether to save the current state (activated or
    deactivated) of all breakpoints, tracepoints, and static
    watchpoints for the next run of the program. The /SAVE qualifier
    specifies that their state is saved, and /NOSAVE specifies that
    their state is not saved. /SAVE may or may not save the state of
    a particular nonstatic watchpoint depending on the scope of the
    variable being watched relative to the main program unit (where
    execution restarts).

2  –  Description

    If you invoked the debugger with the DCL command DEBUG/KEEP and
    subsequently used the debugger RUN command to begin debugging
    your program, you can then use the RERUN command to rerun the
    program currently under debugger control.

    The RERUN command terminates the image you were debugging and
    then restarts that image under debugger control. Execution is
    paused at the start of the main program unit, as if you had used
    the debugger RUN command or the DCL command RUN/DEBUG.

    The RERUN command uses the same version of the image that is
    currently under debugger control. To debug a different version
    of that program (or a different program) from the same debugging
    session, use the RUN command.

    Related commands:

       RUN (debugger command)
       RUN (DCL command)
       (ACTIVATE,DEACTIVATE) BREAK
       (ACTIVATE,DEACTIVATE) TRACE
       (ACTIVATE,DEACTIVATE) WATCH

3  –  Examples

    1.DBG> RERUN

      This command reruns the current program. By default, the
      debugger saves the current state of all breakpoints,
      tracepoints, and static watchpoints (activated or deactivated).

    2.DBG> RERUN/NOSAVE

      This command reruns the current program without saving the
      current state of breakpoints, tracepoints, and watchpoints-in
      effect, the same as using the RUN command and specifying the
      image name.

    3.DBG> RERUN/ARGUMENTS="fee fii foo fum"

      This command reruns the current program with new arguments.