Itschak, Not really enough information to figure out what is causing the disconnect time. The two reasons you give will not cause large disconnect time for a cache hit.
Have you looked at the RMF Cache Reports for the volume when you have this large disconnect time? What is your cache hit break-up? What about cache miss+seq read+seq write activity to other volumes in the same array group. I hope you have Performance Monitor and Cruise Control. If this is a sibling pend problem you can find and fix it without interfering with your online workload. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Itschak Mugzach > Sent: Thursday, 6 October 2005 4:30 PM > To: [email protected] > Subject: High disconnect time on IMS vsam db > > We have a high disconnect time on a IMS vsam database. device is HDS > 9980V. I guess this is because the channel program is performing SEEK > for a specific block, or Search with Key. Can't see any other reason why > this happens. > > Thanks for your advise. > > Itschak > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
