May I know how to check the string value in file definition? Looks like we have wait time for KSDS dataset.
On Sun, Mar 24, 2024, 17:57 Colin Paice < [email protected]> wrote: > > https://www.ibm.com/docs/en/cics-ts/5.6?topic=facility-monitoring-by-using-cics-db2-statistics > says > In the Db2 Connection statistics, check the field “Peak number of tasks on > Pool Readyq”, and also the field “Peak number of Tasks on TCB Readyq”. If > the latter is nonzero, tasks were queued waiting for a Db2 connection to > use with their open TCBs, rather than waiting for a thread. The tasks were > queued because the TCBLIMIT, the maximum number of TCBs that can be used to > control threads into Db2, had been reached. This shows that the number of > threads available (the sum of the THREADLIMIT values for the pool, for > command threads and for all DB2ENTRYs) exceeds the number of TCBs allowed. > TCBLIMIT or the THREADLIMIT values should be adjusted in this case. > > You may not have enough threads in the DB2 pool > > > https://www.ibm.com/docs/en/cics-ts/5.3?topic=waits-resource-types-fcpssusp-fcsrsusp-vsam-strings > says > For non-RLS mode, the number of strings defined for a VSAM data set > (STRINGS parameter in the FILE resource definition) determines how many > tasks can use the data set concurrently. STRINGS can have a value in the > range 1–255. For RLS mode, strings are automatically allocated as needed up > to a maximum of 1024. When all the strings are in use, any other task > wanting to access the data set must wait until a string has been released. > > Check the strings in the FILE definition > > Colin > > On Sun, 24 Mar 2024 at 11:33, raji ece < > [email protected]> wrote: > > > We don't have any CPU constraint for cics address space. > > > > Below values are high for some transactions in the business hours but in > > off hours we don't see much wait time with any other Parameters. > > > > DB2 readyq wait time and FC Vsam string wait time has high values for > some > > transactions during the mid hours and we don't see any wait time for off > > hours. > > > > > > > > On Sun, Mar 24, 2024, 13:33 Massimo Biancucci < > > [email protected]> wrote: > > > > > Hi, > > > > > > let me joke a bit. > > > > > > A man went to the doctor saying: "Doctor if I use my finger and touch > my > > > head I feel pain, if I touch my arm I feel pain, if I touch my chest I > > feel > > > pain, if I touch my leg I feel pain. What do you think the problem is > ?" > > > The doctor: "Your finger is the problem, maybe it's broken" > > > > > > The paining points are at different level and for each one there's > > > something to look at. > > > You didn't report any "value" so we can assume the problem is equally > > > spreaded all over those indicators. > > > > > > Do you have any CPU constraints for CICS Address Spaces ? > > > > > > Best regards. > > > Max > > > > > > > > > Il giorno dom 24 mar 2024 alle ore 07:08 raji ece < > > > [email protected]> ha scritto: > > > > > > > Hello Team, > > > > > > > > Good day, > > > > > > > > We have noticed some of our CICS transaction are getting delayed > recent > > > > days. When we check in sysview , the suspended time is high and the > > > > execution time is very short. > > > > > > > > In the suspended segregation list, we could see below list with more > > wait > > > > time. > > > > > > > > Temp storage wait time > > > > File I/O wait time > > > > CICS exception wait time > > > > CICS TCB change mode delay time > > > > FC VSAM string wait time > > > > DB2 readyq wait time > > > > Resources manager interface time > > > > Resources manager suspended time > > > > ( What are the aspects for all this wait time) > > > > > > > > Also, I have noticed CICS exception and VSAM string wait time has > same > > > > value. > > > > > > > > What are the possible ways to fix this problem? > > > > > > > > > ---------------------------------------------------------------------- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to [email protected] with the message: INFO > IBM-MAIN > > > > > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
