Investigating tasks initiated by ATI

In addition to the general techniques for all tasks described above, there are some additional ones for tasks that should have started by ATI.

Tasks to be started by ATI can be invoked in any of these ways:
  • By issuing EXEC CICS START commands, even if no interval is specified
  • By BMS ROUTE operations
  • By writing to transient data queues with nonzero trigger levels.
There are many reasons why automatically initiated tasks could fail to start. Even when the CICS system is operating normally, an ATI transaction might fail to start for any of the following reasons:
  • It might require a resource that is not available. The resource is usually a terminal, although it could be a queue.
  • It might not be scheduled to start until some time in the future. START commands and output sent with BMS ROUTE are both subject to this sort of scheduling, but transactions started when transient data trigger levels are reached are not.
CICS maintains two chains for scheduling transactions that have been requested, but not started. They are the interval control element (ICE) chain, and the automatic initiate descriptor (AID) chain. The information contained in one or other of the chains can sometimes indicate why your task has failed to start.


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