Why tasks fail to get attached to the transaction manager
A task might fail to get attached to the transaction manager for
one of the following reasons:
- The interval specified on an EXEC CICS START command
might not have expired, or the time specified might not have been
reached, or there might be some error affecting interval control.
Guidance about investigating these possibilities is given in Investigating interval control waits. You need to consider doing this only if INTERVAL or TIME was specified on the START command.
- The terminal specified on an EXEC CICS START command
might not be available. It could be currently OUTSERVICE, or executing
some other task. You can check its status using CEMT INQ
TERMINAL, and perhaps take some remedial action.
Remember that several tasks might be queued on the terminal, some of which might require operator interaction. In such a case, the transaction to be started might not get attached to the transaction manager for a considerable time.
- A remote system specified on an EXEC CICS START command
might not be available, or an error condition might have been detected
in the remote system. In such a case, the error would not be reported
back to the local system.
You can use CEMT INQ TERMINAL to inquire on the status of the remote system.