Ending a z/OS Debugger session within multiple enclaves
If you specify the NOPROMPT suboption of the TEST runtime
option for the next process on the host, z/OS® Debugger restores
the saved breakpoints after it gains control of that next process.
However, z/OS Debugger might
gain control of the process after many statements have been run. Therefore, z/OS Debugger might
not run some or all of the following breakpoints:
STATEMENT/LINEENTRYEXITLABEL
If you have not used these breakpoint types, you can specify NOPROMPT.
In a single enclave, QUIT closes z/OS Debugger. For CICS® non-Language Environment® programs
(assembler or non-Language Environment COBOL), QUIT closes z/OS Debugger and
the task ends with an ABEND 4038, regardless of the link level.
In a nested enclave, however, QUIT causes z/OS Debugger to signal a severity 3 condition that
corresponds to Language
Environment message
CEE2529S. The system is trying to cleanly terminate all enclaves in the process.
This applies to any Language
Environment
programs on CICS, IMS and MVS.
Normally, the condition causes the current enclave to terminate.
Then, the same condition will be raised in the parent enclave, which
will also terminate. This sequence continues until all enclaves in
the process have been terminated. As a result, you will see a CEE2529S message
for each enclave that is terminated.
For CICS and MVS only: Depending on Language Environment run-time settings, the application might be terminated with an ABEND 4038. This termination is normal and should be expected.