There are several levels at which the dumping environment can
be set up:
- System dumps (apart from CICS kernel domain dumps) can be globally
suppressed or enabled at system initialization by using the DUMP system
initialization parameter.
- System dumps (apart from CICS kernel domain dumps) can be globally
suppressed or enabled dynamically through the EXEC CICS SET SYSTEM
DUMPING command.
- Transaction dumps can be suppressed or enabled dynamically for
individual transactions. This is done by using the EXEC CICS SET TRANSACTION
DUMPING system programming command, or the CEMT SET TRDUMPCODE command
or by using the DUMP attribute of the RDO definition for the transaction.
- System dumps (apart from CICS kernel domain dumps) can be suppressed
for specific dump codes from a dump domain XDUREQ global user exit
program.
- System dumps (apart from CICS kernel domain dumps) can be suppressed
or enabled, and other dumping requirements specified, by means of
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.
- Dumps of the builder parameter set at specific stages in the build
process of terminal or connection definition can be enabled. This
is done using the CSFE ZCQTRACE facility. For details, see The CSFE ZCQTRACE facility.
When more than one CICS system runs under one instance of
the MVS™ operating system, two CICS systems can take
duplicate system dumps.
Each CICS system dump header includes a symptom string. The symptom
string will be created only if the system dump code has the DAE option
specified in the dump table entry. The default action is that symptom
strings are not produced. This can, however, be altered by means of
the DAE= system initialization parameter.
The symptom strings provide sufficient information to enable the
detection of duplicate dumps. You can take advantage of this in either
of two ways:
- Use MVS Dump Analysis Elimination (DAE) to detect and suppress
duplicate dumps. (If the symptom string has been suppressed by the
dump table option, DAE will not suppress the system dump.)
You
can control DAE with an ADYSETxx parmlib member. For information about
DAE, see OS/390 MVS Diagnosis: Tools and Service Aids.
- Manually compare the headers of system dumps, so that you are
aware that you have duplicate dumps. Doing it this way, you avoid
repeating the same analysis, but still have a separate dump listing
for each CICS system.
[[ Contents Previous Page | Next Page Index ]]