Storage freeze, the storage violation trap and the global trap/trace exit are all debugging functions that are controlled by the CSFE transaction. These functions are described in the following sections.
You can use CSFE DEBUG to freeze storage that is normally freed during the processing of a transaction. The frozen storage is not freed until the end of the transaction. This freezing of storage can help you in the subsequent diagnosis of problems that may have occurred during processing.
CSFE DEBUG TRANID >>-CSFE debug--+-,TRANID=xxxx-+--+------------------+---------->< '-,TASKREQ=yyy-' | .-OFF-. | '-,STGFRZ=-+-----+-' '-ON--'
You must code the options in the order shown in the syntax display above.
Use CSFE DEBUG to activate and deactivate the storage violation trap, which is in the trace program (DFHTRP), the exec interface program (DFHEIP), and the resource manager interface program (DFHERM).
This trap lets you verify the user storage associated with the currently active task. The storage violation trap is entered before the trace program returns to its caller after making a trace entry.
When a storage violation is detected by the trap, an exception trace entry is made, a CICS system dump is produced (if dumping has not been disabled), and the storage violation trap is switched off.
CSFE DEBUG CHKSTSK >>-CSFE debug--+-,CHKSTSK=-+-CURRENT-+-+----------------------->< | '-NONE----' | '-,CHKSTRM=-+-CURRENT-+-' '-NONE----'
For information on the CSFE options and their actions, see the CICS® Problem Determination Guide.
You can use CSFE DEBUG with the TRAP or GTRAP operand to activate and deactivate the global trap/trace program exit routine or the global kernel exit routine respectively.
These exits are intended to be used only under the guidance of IBM support personnel.
CSFE DEBUG TRAP >>-CSFE DEBUG--+-,TRAP=-+-ON--+--+----------------------------->< | '-OFF-' | '-,GTRAP=-+-ON--+-' '-OFF-'