>I think you need to expand that question to: >1. what does it cost to do a VSAM I/O to real disk (or cache in your case, since the hit ratio is almost 100%)?
The same as the cost going to disk -- it's just faster. >2. what does it cost to do a VSAM I/O but finds a hit in a memory buffer? The same as going to cache -- it's just faster. >3. what does it cost to do a VSAM I/O but finds a hit in memory, e.g. CMDT? This was my recommendation! >If this region uses less than 5% of cpu, and the end-users do not complain >about R/T, then do you really have problem? Ah, there's the key. My original post stated that response was occasional erratic, and users were complaining. I am trying to fix it, but management wants a cost justification. Hence, the question on cost for an I/O. Since we are in an out-sourced arrangement, MIPS have a real cost. So, does anybody have an answer? Or, do we just continue to dance? - -teD O-KAY! BLUE! JAYS! Let's PLAY! BALL! ---------------------------------------------------------------------- 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
