QUIT command
The QUIT
command ends a z/OS® Debugger 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.
- expression
- A valid z/OS Debugger 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
, z/OS Debugger raises a CEE2F1 exception to terminate each active enclave. DEBUG
- If you specify
DEBUG
, z/OS Debugger ends and your program keeps running. Any calls to restart z/OS Debugger 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 specifyTASK
, z/OS Debugger 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, z/OS Debugger debugging will resume.
Usage notes
- z/OS Debugger will only resume in a new pseudo-conversational task if 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 z/OS Debugger commands file, no prompt is displayed. This behavior applies to the z/OS Debugger preferences files, primary commands files, andUSE
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 thePLIRETC
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 z/OS Debugger, you must first restart your program. - If you enter the
QUIT
orQQUIT
command while you are debugging a non-Language Environment® assembler or LangX COBOL program running under CICS, z/OS Debugger behaves the same as if you entered aQUIT 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 messageConnection with debug engine was lost.
Examples
- End a z/OS Debugger session.
QUIT;
- End a z/OS Debugger session
and use the value in variable
x
as the application return code.QUIT (x);
- End a z/OS Debugger 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
- z/OS Debugger commands supported in remote debug mode