Dealing with incorrect output

Incorrect output has been categorized into a number of areas. Look at the appropriate section to diagnose why this problem is occurring.

Trace output is incorrect
If you have been unable to get the trace output you need, you can find guidance about solving the problem in this section. You can be very selective about the way CICS® does tracing, and the options need to be considered carefully to make sure you get the tracing you want.
Dump output is incorrect
Read this section if you do not get the dump output you expect.
Incorrect data is displayed on a terminal
There are many reasons why you might get the wrong data displayed, some with system-related causes and some with application-related causes. If you think that it is system-related, read this section for some suggestions on likely areas in which to start your investigations.
Specific types of incorrect output for terminals
This section contains some suggestions about what to do for specific types of incorrect output, and what might be at fault.
Incorrect data is present on a VSAM data set
If READ UPDATE is not used, an error can occur because VSAM allows a record to be read by one transaction while another transaction is updating it.
An application does not work as expected
It is not possible to give specific advice on dealing with this sort of problem, but the points and techniques that follow should help you to find the area where the failure is occurring.
Your transaction produces no output at all
If your transaction produced no output at all, you need to carry out some preliminary checks before looking at the problem in detail. You might be able to find a simple explanation for the failure.
Your transaction produces some output, but it is wrong

Parent topic: Dealing with the problem