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.
- Are there any messages explaining why there is no output?
Look carefully in each of the transient data destinations CSMT, CSTL, and CDBC for any messages that might relate to the task. You could find one there that explains why you received no output.
If you can find no such message, the next step is to get some information about the status of the transaction that produced no output, your terminal, and the CICS® system.
- Can you use the terminal where the transaction should have started? See Can you use the terminal where the transaction should have started? for the steps to follow.
- If
you obtained no output and the task is still in the system, it is either waiting
for a resource, or looping. You should get an indication of which of these
two conditions is the most likely from the status for the task returned by CEMT
INQ TASK.
- If you have a suspended task, treat this as a “wait” problem. Use the techniques described in Dealing with waits to investigate it further.
- If you have a running task, it is likely to be looping. See Dealing with loops to find out what to do next.
- Did the task run? There are a variety of techniques for finding this information. These are described in Techniques to find out whether a transaction started