When a condition occurs
When an HLL condition occurs and you have defined a breakpoint
with associated actions, those actions are first performed. What happens
next depends on how the actions end.
- Your program's execution can be terminated with a
QUITcommand. If you are debugging a CICS® non-Language Environment® assembler or non-Language Environment COBOL programs,QUITends z/OS® Debugger and the task ends with an ABEND 4038. - Control of your program's execution can be returned to the HLL
exception handler, using the
GOcommand, so that processing proceeds as if z/OS Debugger had never been invoked (even if you have perhaps used it to change some variable values, or taken some other action). - Control of your program's execution can be returned to the program
itself, using the
GO BYPASScommand, bypassing any further processing of this exception either by the user program or the environment. - PL/I allows
GO TO out of block;, so execution control can be passed to some other point in the program. - If no circumstances exist explicitly directing the assignment of control, your primary commands file or terminal is queried for another command.
If, after the execution of any defined breakpoint, control returns
to your program with a GO, the condition is raised
again in the program (if possible and still applicable). If you use
a GOTO to bypass the failing statement, you also
bypass your program's error handling facilities.
Refer to the following topics for more information related to the material discussed in this topic.
- Related references
- Language Environment conditions and their C and C++ equivalents
- PL/I conditions and condition handling
- z/OS Language Environment Programming Guide
- Enterprise COBOL for z/OS Language Reference