The dump code options you can specify

You can specify what dump action CICS® will take for each individual dump code, by defining and installing a DUMPCODE through the resource definition online (RDO) interface, by using the CEMT transaction, or by using a system programming command.

The options you can specify differ slightly, depending on whether you are defining the action for a transaction dump code or for a system dump code.
For a transaction dump code:
You can specify the following options:
  • Whether a transaction dump is to be taken.
  • Whether a system dump is to be taken, with or without a transaction dump.
  • Whether a system dump is to be taken on every CICS region in the sysplex related to the CICS region on which the transaction dump is taken. A related CICS region is one on which the unit of work identifiers, in the form of APPC tokens, of one or more tasks match those in the CICS region that takes the transaction dump.
  • Whether CICS is to be terminated.
  • The maximum number of times the transaction dump code action can be taken during the current run of CICS, or before the count is reset.
Tip: You can specify the areas you want written to a transaction dump when you use the EXEC CICS DUMP TRANSACTION command to get a transaction dump.

You cannot specify in the dump table which areas are to be written to the transaction dump for particular transaction dump codes. You always get a complete transaction dump whenever a transaction abend occurs, if the dump code requires a transaction dump to be taken.

For a system dump code:
You can specify the following options:
  • Whether a system dump is to be taken.
  • Whether a system dump is to be taken on every CICS region in the sysplex related to the CICS region on which the system dump is taken. A related CICS region is one on which the unit of work identifiers, in the form of APPC tokens, of one or more tasks match those in the CICS region that takes the system dump.
  • Whether CICS is to be terminated.
  • The maximum number of times the system dump code action can be taken during the current run of CICS, or before the count is reset.
  • Whether the system dump is eligible for suppression by DAE.
Note:
  1. Only a transaction dump code can cause both a transaction dump and a system dump to be taken.
  2. If a severe error is detected, the system can terminate CICS even if you specify that CICS is not to be terminated.
  3. Values of 0–998 for “maximum times dump code action can be taken” are literal, but a value of 999 (the default) means there is no limit.
  4. You cannot suppress CICS kernel domain dumps.

How dump code options are preserved

All the options you specify are recorded in the appropriate dump table, and written in the CICS global catalog. Any dump table entries you have changed or created during a CICS run are preserved when CICS is subsequently shut down. They are available during the next run unless a cold start of CICS is performed, in which case they are deleted from the global catalog.

Note however you have the option of installing dump codes afresh on a cold start using RDO-defined DUMPCODEs in a group that is installed as part of the GRPLIST.

Dump table additions and changes are lost in the following circumstances:
  • When a cold start of CICS is performed and dumpcodes are not re-installed as part of RDO GRPLIST installation.
  • When the CICS global catalog is redefined, although this is likely to be done only in exceptional circumstances.
  • When CICS creates a temporary dump table entry for you, because you have asked for a dump for which there is no dump code in the dump table.