Library /sys$common/syshlp/DBG$HELP.HLB  —  DEBUG  QUIT  Description
    The QUIT command is simlar to the EXIT command, except that QUIT
    does not cause your program to execute and, therefore, does not
    execute any application-declared exit handlers in your program.

    Ending a Debugging Session:

    To end a debugging session, enter the QUIT command at the
    debugger prompt without specifying any parameters. This causes
    orderly termination of the session: the debugger exit handler
    is executed (closing log files, restoring the screen and keypad
    states, and so on), and control is returned to DCL level. You
    cannot then continue to debug your program by entering the DCL
    command DEBUG or CONTINUE (you must restart the debugger).

    Using the QUIT Command in Command Procedures and DO Clauses:

    When the debugger executes a QUIT command (without any
    parameters) in a command procedure, control returns to the
    command stream that invoked the command procedure. A command
    stream can be the terminal, an outer (containing) command
    procedure, or a DO clause in a command or screen display
    definition. For example, if the command procedure was invoked
    from within a DO clause, control returns to that DO clause, where
    the debugger executes the next command (if any remain in the
    command sequence).

    When the debugger executes a QUIT command (without any
    parameters) in a DO clause, it ignores any remaining commands
    in that clause and displays its prompt.

    Terminating Specified Processes:

    If you are debugging a multiprocess program, you can use the
    QUIT command to terminate specified processes without ending
    the debugging session. The same techniques and behavior apply,
    whether you enter the QUIT command at the prompt or use it within
    a command procedure or DO clause.

    To terminate one or more processes, enter the QUIT command,
    specifying these processes as parameters. This causes orderly
    termination of the images in these processes without executing
    any application-declared exit handlers associated with these
    images. Subsequently, the specified processes are no longer
    identified in a SHOW PROCESS/ALL display.

    In contrast to the EXIT command, the QUIT command does not cause
    any process to start execution.

    Related commands:

       DISCONNECT
       @ (Execute Procedure)
       Ctrl/C
       Ctrl/Y
       Ctrl/Z
       EXIT
       RERUN
       RUN
       SET ABORT_KEY
       SET PROCESS
Close Help