AT DELETE command
Gives z/OS® Debugger control
when a load module is removed from storage by a Language Environment®, MVS, or CICS® delete service, such as on completion
of a successful C release(), COBOL CANCEL,
PL/I RELEASE, assembler DELETE macro,
or EXEC CICS RELEASE.
- *
- Sets a breakpoint at every
DELETEof any load module. - command
- A valid z/OS Debugger command.
Usage
notes
- z/OS Debugger gains
control for deletes that are affected by the Language
Environment delete
service, MVS delete service,
or
EXEC CICS RELEASE. If the Dynamic Debug facility is deactivated (by entering theSET DYNDEBUG OFFcommand) or SVC screening is disabled, z/OS Debugger is not notified of deletes affected by the MVS delete service. Refer to IBM® z/OS Debugger Customization Guide for instructions on how to control SVC screening. AT DELETEcannot specify the initial load module.- If this breakpoint is set in a parent enclave, it can be triggered and operated on with commands while the application is in a child enclave.
- For a CICS application on z/OS Debugger, this breakpoint is cleared at the end of the last process in the application. For a non-CICS application on z/OS Debugger, it is cleared at the end of a process.
- The
AT DELETEcommand cannot be used while you replay recorded statements by using thePLAYBACKcommands.
Examples
- Each time a load module is deleted, request input from the terminal.
AT DELETE *; - Stop watching variable
var1:>xwhen load modulemymodis deleted.AT DELETE mymod CLEAR AT CHANGE (var1:>x);
Refer to the following topics for more information related to the material discussed in this topic.
- Related references
- every_clause syntax
- load_spec
- PLAYBACK commands
