Suppressing system dumps that precede ASRx abends

The MVS system dump data sets can become full with unwanted SDUMPs that precede ASRA, ASRB, and ASRD abends (after message DFHAP0001 or DFHSR0001).

If CICS® storage protection is active, you can suppress the system dumps caused by errors in application programs (after message DFHSR0001), while retaining the dumps caused by errors in CICS code (after message DFHAP0001). To do this, use a CEMT SET SYDUMPCODE command, or an EXEC CICS SET SYSDUMPCODE command to suppress system dumps for system dump code SR0001. For example:

CEMT SET SYDUMPCODE(SR0001) ADD NOSYSDUMP

CICS uses dump code SR0001 if an application program was executing in user-key at the time of the program check or MVS abend. This is possible only if storage protection is active. If the program was executing in CICS-key, dump code AP0001 is used instead.

When storage protection is not active, you can suppress system dumps for system dump code AP0001. However, this suppresses dumps for errors in both application and CICS programs. The XDUREQ global user exit can be used to distinguish between AP0001 situations in application and CICS programs.

For more information about the storage protection facilities available in CICS, see Storage protection.

If you want SDUMPs for one of these transaction abends but not the other, select the one you want by using either a CEMT TRDUMPCODE or an EXEC CICS TRANDUMPCODE command. This specifies, on an entry in the dump table, that SDUMPs are taken for ASRA, ASRB, or ASRD abends. For example, to add an entry to the dump table and ensure that SDUMPs are taken for ASRB abends.specify the following:

CEMT SET TRDUMPCODE(ASRB) ADD SYSDUMP

However, in this case, the SDUMPs are taken at a later point than SDUMPs usually taken for system dump code AP0001 and SR0001.

For information about the DFHAP0001 and DFHSR0001 messages, see CICS messages and Finding where a program check occurred.