A task stops running at a terminal

When a task stops running at a terminal, you will notice either or both of these symptoms:
  • No output is obtained at the terminal
  • The terminal accepts no input

First, make sure that the task is still in the system. Use CEMT INQ TASK to check its status, and make sure that it has not ended without writing back to the terminal.

If the terminal has a display unit, check to see whether a special symbol has been displayed in the operator information area that could explain the fault. If the operator information area is clear, next check to see that no message has been sent to any of the transient data destinations used for error messages, for example:
  • CDBC, the destination for DBCTL related messages
  • CSMT, the destination for terminal error and abend messages
  • CSTL, the destination for terminal I/O error messages
  • CSNE, the destination for error messages written by DFHZNAC and DFHZNEP
For details of the destinations used by CICS, see Setting up data sets for transient data. If you can find no explanation for the problem, the fault is probably associated with the task running at the terminal. These are the possibilities:
  • The task is in a wait state.
  • The task is in a loop.
  • There is a performance problem.

Read Distinguishing between waits, loops, and poor performance to find out which of these is the most likely explanation. You can then read to the appropriate section for advice about dealing with the problem.



dfhs1c0019.html | Timestamp icon Last updated: Monday, 5 June 2017