QUIT command

The QUIT command ends a Debug Tool session and, if an expression is specified, sets the return code. In full-screen mode, it also displays a prompt panel that asks if you really want to quit the debug session. In line, batch, and remote debug mode, the QUIT command ends the session without prompting.


>>-QUIT--+------------------+--;-------------------------------><
         +-(--expression--)-+      
         +-ABEND------------+      
         '-DEBUG--+------+--'      
                  '-TASK-'

expression

A valid Debug Tool expression in the current programming language.

If expression is specified, this value is used as the application return code value. The actual return code for the run is determined by the execution environment.

You cannot use expression in remote debug mode.

ABEND

If you specify ABEND, Debug Tool raises a CEE2F1 exception to terminate each active enclave.

DEBUG

If you specify DEBUG, Debug Tool ends and your program keeps running. Any calls to restart Debug Tool are ignored. By default, when running under CICS®, a pseudo-conversational application will run until the end of the conversation (until EXEC CICS RETURN without TRANSID is issued to return to CICS).

TASK

TASK applies to CICS pseudo-conversational applications. If you specify TASK, Debug Tool processing will be terminated until the end of the current CICS pseudo-conversational task (EXEC CICS RETURN TRANSID). When a new task is started in the pseudo-conversation, Debug Tool debugging will resume.

Usage notes

Debug Tool will only resume in a new pseudo-conversational task if CADP or DTCN successfully match on a pattern.
QUIT is always logged in a comment line except where it appears in a command list. This enables you to reuse the log file as a primary commands file.
If QUIT is entered from a Debug Tool commands file, no prompt is displayed. This behavior applies to the Debug Tool preferences files, primary commands files, and USE files.
For PL/I, the expression will be converted to FIXED BINARY (31,0), if necessary. In addition, if an expression is specified, it is used as if your program called the PLIRETC built-in subroutine.
For PL/I, the value of the expression must be nonnegative and less than 1000.
If you enter the QUIT DEBUG command and then want to restart Debug Tool, you must first restart your program
If you enter the QUIT or QQUIT command while you are debugging a non-Language Environment assembler or LangX COBOL program running under CICS, Debug Tool behaves the same as if you entered a QUIT ABEND command and a U4038 abend occurs.
In remote debug mode, if any form of the QUIT command is found in a preferences or commands file, the remote debugger displays the message "Connection with debug engine was lost."

Examples

End a Debug Tool session.
```
QUIT;
```
End a Debug Tool session and use the value in variable x as the application return code.
```
QUIT (x);
```
End a Debug Tool session without ending the program.
```
QUIT DEBUG;
```

Refer to the following topics for more information related to the material discussed in this topic.

Related references
expression
Debug Tool commands supported in remote debug mode