Collecting the evidence

You should find all the evidence you need to investigate the transaction abend in the information sent to the various transient data queues for error messages, and in the transaction dump. If no transaction dump has been produced, it is possible that transaction dumping has been suppressed for the transaction (via the transaction definition), or the dump code entry in the transaction dump code table suppresses dumping. For guidance about changing the dumping options so that you get a transaction dump, see Using dumps in problem determination.

The transaction abend code and the abend message are recorded in the CSMT log. Make a note, too, of any other messages you find there that might relate to the abend, as they could provide additional valuable evidence.

Check also to see if any relevant messages have been sent to the transient data destinations used by CICS® to record messages. For a list of destinations used by CICS, see the CICS System Definition Guide. Look in particular for any messages about files, terminals, or printers that you might be attempting to use.

Symptom string

CICS produces a symptom string as part of the transaction dump. The symptom string gives some details about the circumstances of the transaction dump. It might show, for example, that the dump was taken because the transaction abended with the abend code ASRA. If you refer the problem that caused the dump to be taken to the IBM® Support Center, they will use the symptom string to search the RETAIN® database for problems similar to it. For an introduction to symptom strings and their contents, see Looking at the symptom string in the dump.

Related concepts
What the abend code can tell you
Where dumps are written
Related tasks
The dump code options you can specify
Formatting transaction dumps
Related references
Worksheet for transaction abends
The transaction dump table
Transaction abend codes
[[ Contents Previous Page | Next Page Index ]]