We all knew in CICS region a transaction runs in DISPATCHER condition when the task is waiting to get dispatched, eg. to run on QR TCB. The problems we are seeing is likely that some tasks are monopolizing the QR TCB and therefore building up a queue of waiting tasks. Some reasons can be too high value for run away tasks (i.e. something is looping), too much work (QR TCB runs 100%), CICS does not get enough CPU.
For our CICS test region we dont have any TOOLS to monitor the Transaction which consumes more CPU. Mostly the DISPATCHER condition occurs during CICS DB2 load activity.
Could anyone please throw some light to avoid the dispatcher condition to occur.