Setting up the dumping environment
There are several levels at which the dumping environment can be set up.
About this task
Procedure
- To globally suppress or enable system dumps at system initialization, use the DUMP system initialization parameter This does not apply to CICS kernel domain dumps.
- To globally suppress or enable system dumps dynamically, use the EXEC CICS SET SYSTEM DUMPING command. This does not apply to CICS kernel domain dumps.
- To enable or suppress transaction
dumps for individual transactions, use one of the following options:
- EXEC CICS SET TRANSACTION DUMPING system programming command
- CEMT SET TRDUMPCODE command
- DUMP attribute of the RDO definition for the transaction.
- To suppress specific dump codes from a dump domain, use the XDUREQ global user exit program. This does not apply to CICS kernel domain dumps.
- To suppress or enable system dumps (apart from CICS kernel domain dumps), and specifying other dumping requirements, use dump codes. A dump code defines what action CICS is to take under any of the circumstances in which a dump might be required. Dump codes are kept in one of two dump tables, one for transaction dump codes and the other for system dump codes. For details, see The dump code options you can specify.
- To enable dumps of the builder parameter at specific stages in the build process of terminal or connection definitions, use the CSFE ZCQTRACE facility. For details, see The CSFE ZCQTRACE facility.
- Detecting and avoiding duplicate system dumps
When more than one CICS system runs under one instance of the MVS™ operating system, two CICS systems can take duplicate system dumps.
dfhs18a.html |
Last updated: Monday, 5 June 2017