Avoiding DISPATCHER condition



Support for CICS/ESA, CICS/TS & Transaction Gateway, CICS Configuration Manager and CICS Performance Analyzer

Avoiding DISPATCHER condition

Postby jaggz » Fri Mar 30, 2012 2:22 pm

Hello All,

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.

Jaggz
User avatar
jaggz
 
Posts: 356
Joined: Fri Jul 23, 2010 8:51 pm
Has thanked: 8 times
Been thanked: 3 times

Re: Avoiding DISPATCHER condition

 

Re: Avoiding DISPATCHER condition

Postby Monitor » Fri Mar 30, 2012 2:51 pm

Monitor
 
Posts: 98
Joined: Wed Jan 18, 2012 8:59 pm
Has thanked: 0 time
Been thanked: 7 times

Re: Avoiding DISPATCHER condition

Postby jaggz » Fri Mar 30, 2012 3:17 pm

The ICVR values are not helpful for the program which are running in Loop. ICVR is reset everytime and CICS is not able to detect the Loop.
User avatar
jaggz
 
Posts: 356
Joined: Fri Jul 23, 2010 8:51 pm
Has thanked: 8 times
Been thanked: 3 times

Re: Avoiding DISPATCHER condition

Postby jaggz » Fri Mar 30, 2012 3:31 pm

Hello,

I am looking a way to purge the yielding loops.
User avatar
jaggz
 
Posts: 356
Joined: Fri Jul 23, 2010 8:51 pm
Has thanked: 8 times
Been thanked: 3 times

Re: Avoiding DISPATCHER condition

Postby BillyBoyo » Fri Mar 30, 2012 3:38 pm

Surely you don't get many "loops" in your CICS, even in development?

When it happens, the person who pressed enter (or emulated pressing enter) knows about it. Why not ask anyone to give you a call when they set off a loop. Make some sort of "forfeit" for anyone who sets off a loop and doesn't tell you.
BillyBoyo
Global moderator
 
Posts: 3762
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 256 times

Re: Avoiding DISPATCHER condition

Postby Monitor » Sat Mar 31, 2012 2:41 pm

Why not enable Auxiliary trace for a while until the problem occurs. You say the ICVR doesnt work, which meens that the task causing the problem issues CICS-commands, as the timer is reset when you are back in your program again.
An analysis of the trace output could help you find the "looping" task/program.
Monitor
 
Posts: 98
Joined: Wed Jan 18, 2012 8:59 pm
Has thanked: 0 time
Been thanked: 7 times


Return to CICS

 


  • Related topics
    Replies
    Views
    Last post