I don't remember any reduction in cpu instructions for VSAM just enhanced functionality. One of the reasons DB2 uses the media manager interface.
You ddin't mention the transaction rate. Is this one transaction doing batch workload? or lots of small transactions? Since the cache hit ratio is 98%, it obviously has a limited requirement for working set. I suspect it is write intensive because CICS has to force write at transaction boundrry. This is one case where a database like DB2 can be cheaper because DB2 will buffer writes to the file. (only log activity is forced in DB2). If it is update driven, the other choice would be to pass the data to a background transaction that processes multiple input transaction and contols when CICS does the writes. Mike ---------------------------------------------------------------------- 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
