Can you use the terminal where the transaction should have started?
Go to the terminal where the transaction should have started, and note whether the keyboard is locked. If it is, press RESET. Now try issuing CEMT INQ TASK (or your site replacement) from the terminal.
If you cannot issue CEMT INQ TASK from the terminal, one of these
explanations applies:
- The task that produced no output is still attached to the terminal.
- The terminal where you made the inquiry is not in service.
- There is a system-wide problem.
- You are not authorized to use the CEMT transaction. (This may be because you have not signed on to the terminal and the CEMT transaction is not authorized for that terminal. If you have signed on to the terminal, you are probably authorized to use CEMT.)
Try to find a terminal where you can issue CEMT INQ TASK. If no terminal
seems to work, there is probably a system-wide problem. Otherwise, see if
the task you are investigating is shown in the summary.
- If the task is shown, it is probably still attached, and either looping or waiting. Turn to Distinguishing between waits, loops, and poor performance to see what to do next.
- If the task is not shown, there is a problem with the terminal where you first attempted to issue CEMT INQ TASK.
If you are able to issue CEMT INQ TASK from the terminal where the
transaction was attached, one of these explanations applies:
- The transaction gave no output because it never started.
- The transaction ran without producing any output, and terminated.
- The transaction started at another terminal, and might still be in the system. If it is still in the system, you can see it in the task summary that you got for CEMT INQ TASK. It is probably looping or waiting. See Distinguishing between waits, loops, and poor performance for advice about what to do next. If you do not see the task in the summary, go to No output - what to do if the task is not in the system.