You do not get a dump when an abend occurs

Read this section if you are experiencing any of these problems:
  • A transaction abended, but you do not get a transaction dump.
  • A transaction abended and you get a transaction dump, but you do not get the system dump you want at the same time.
  • A system abend occurred, but you do not get a system dump.
There are, in general, two reasons why dumps might not be taken:
  • Dumping is suppressed because of the way the dumping requirements for the CICS region were defined. The valid ways that dumping can be suppressed are described in detail in the sections that follow.
  • A system error could have prevented a dump from being taken. Some of the possibilities are:
    • No transaction or system dump data sets were available.
    • An I/O error occurred on a transaction or a system dump data set.
    • The system dump data set was being written to by another region, and the DURETRY time was exceeded.
    • There was insufficient space to write the dump in the dump data set. In such a case, you might have obtained a partial dump.

      Depending on the areas that are missing from the dump, the dump formatting program might subsequently be able to format the data that is there, or it might not be able to format the data at all.

    For each of these system errors, there should be a message explaining what has happened. Use the CMAC transaction or see CICS messages for guidance about the action to take.


dfhs12t.html | Timestamp icon Last updated: Monday, 5 June 2017