Help

 

ICP_TERM

If you have a task that is not running, and interval control seems to be involved, the following is a list of possible cases, and suggestions to consider before you carry out a detailed investigation. If these do not give you enough information in order to solve the problem, turn to "Finding the reason for a DELAY request not completing" in the CICS Problem Determination Guide for further guidance.

If, in the course of your preliminary investigations, you find that the task is waiting because the terminal where it is due to start is unavailable, turn to "Terminal waits" in the CICS Problem Determination Guide.

  • A terminal task that should have been initiated with an EXEC CICS START command did not start when you expected it to. CEMT INQ TASK does not recognize the task, because it has not yet been attached.

One approach is to identify the terminal where the subject task should have started, and see if that terminal is, for some reason, unavailable. You can use CEMT INQ TERMINAL to find the status of the terminal.

  • A task that issued EXEC CICS POST did not have its ECB posted when you expected it to. Check to make sure the interval or time you specified was what you intended.

  • A task that issued EXEC CICS WAIT EVENT was not resumed when you thought it should have been. Assuming the WAIT was issued sometime after a POST, first check to make sure that the interval or time specified on the POST was what you intended. If it was, next check to see whether the ECB being waited on was posted. If it was, that indicates a possible CICS error.