> -----Original Message----- > From: CICS List On Behalf Of Martin, Mike > > Jorg, > > How many engines does your system have? Is it possible that > the region having increased response time is starting to tax > the capacity of a single engine? > > Mike Martin

Or a single TCB (the QR), if "Threadsafe" is not being exploited.

-jc-

> > -----Original Message----- > From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU] On Behalf Of > Jorg Lueke > Sent: Wednesday, April 13, 2005 11:07 AM > To: CICS-L@LISTSERV.UGA.EDU > Subject: Redispatch Wait Times > > > We have an environement where 3 CICS regions run on 1 Lpar. > Basically they pass the transactions off from one to the next > and then back out to the user. > > In one of the regions, as volumes increase the CICS response > time increased. DB2 response times went down and WLM shows > no CPU dispatching issues and there are no storage/enqueue issues. > > We tracked this down to an increase in CICS Redispatch wait > time for a particular transactions. Most of ours gave a > redisptahc wait of 0 to > .05 as does this transaction. However as the volume picks up > this transaction sees the redispatch waits rise to over .2 seconds. > > First, does redispatch wait mean the amount of time waiting > to restart running under CICS after coming back (from DB2 in > this case)? > > Secondly, what can be causes of this wait time in a > environment with no CPU/Storage shortages? > > > <FONT SIZE=1 FACE="ARIAL">^^^^^^^^^^^^^ > This email may contain confidential and privileged material > for the sole use of the intended recipient. If you are not > the intended recipient, please contact the sender and delete > all copies. Any review or distribution by others is strictly > prohibited. Personal emails are restricted by policy of the > State Employees' Credit Union (SECU). Therefore SECU > specifically disclaims any responsibility or liability for > any personal information or opinions of the author expressed > in this email. > > > </FONT> >