Collecting the evidence
The evidence you need to investigate the transaction abend should be in the information sent to the various transient data queues for error messages, and in the transaction dump.
Procedure
- Check the transaction dump to find information about the
transaction abend. 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 can use the symptom string to search the RETAIN database for any similar problems.
For an introduction to symptom strings and their contents, see Symptom strings.
If no transaction dump has been produced, it is possible that transaction dumping has been suppressed for the transaction (through 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.
- Check the CSMT log. The transaction abend code and the abend message are recorded in the log. Make a note of any other messages in the log that might relate to the abend, because they might provide additional valuable evidence.
- Check whether any relevant messages were sent to the transient
data destinations used by CICS to
record messages. Look in particular for any messages about
files, terminals, or printers that you might be attempting to use.
For a list of destinations used by CICS, see Setting up data sets for transient data.
dfhs1l5.html |
Last updated: Monday, 5 June 2017