Using CSFE debug functions

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.

Storage freeze

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.

Read syntax diagramSkip visual syntax diagramCSFE 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.

STGFRZ={OFF|ON}
specifies that you want the storage freeze function to be set on or off. If you omit this option, storage freeze is set to OFF by default. To improve efficiency, storage freeze should be switched OFF when not required.
TASKREQ=yyy
This is an alternative method of identifying the transaction. "yyy" is the PA or PF key definition on a 3270 display device which identifies the transaction for which storage freeze is to apply. For example, TASKREQ=PA1.
TRANID=xxxx
Identifies the transaction for which storage freeze is to apply.

Storage violation trap

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.

Read syntax diagramSkip visual syntax diagramCSFE DEBUG CHKSTSK
 
>>-CSFE debug--+-,CHKSTSK=-+-CURRENT-+-+-----------------------><
               |           '-NONE----' |
               '-,CHKSTRM=-+-CURRENT-+-'
                           '-NONE----'
 
CURRENT
Specifies that validity checks are to be performed on the user storage (not the CICS storage) for the current task whenever the trace program is entered. Validity checks are to be performed for the currently active task, as follows:

For information on the CSFE options and their actions, see the CICS® Problem Determination Guide.

NONE
deactivates the user storage checking function.
CHKSTRM={CURRENT|NONE}
The terminal subpools, above and below the line, are to be checked for the CURRENT task or for NONE (no tasks).

Global trap/trace program exit and global kernel exit

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.

Read syntax diagramSkip visual syntax diagramCSFE DEBUG TRAP
 
>>-CSFE DEBUG--+-,TRAP=-+-ON--+--+-----------------------------><
               |        '-OFF-'  |
               '-,GTRAP=-+-ON--+-'
                         '-OFF-'
 
TRAP={ON|OFF}
The global trap/trace program exit routine is to be activated or deactivated.
GTRAP={ON|OFF}
The global kernel exit routine is to be activated or deactivated. On each domain call and return, and each subroutine call and return, the kernel invokes the global kernel exit routine, if it is activated.
TRAP= ON or off
specifies that the global/trap exit routine is to be activated or deactivated.

Related tasks
Using CICS supplied transactions
CSFE--terminal and system test
Using CSFE terminal test
Tracing with CSFE
[[ Contents Previous Page | Next Page Index ]]