Tony, I appreciate all the suggestions. I had been thru all of the knife-removal checks .. all except for the TIMELOCK.
I talked it a little bit with CA... then went to the TIMELOCK(10,160,320,3000) .. and things got better. So, I went back and had some more conversations to better understand the lock what is happening. After the second discussion, I decided that the lock-loops (a system that gets the lock is going to have a tendency to get it again before the other systems can get in) were still an issue. And our CF response time is very good 200-300 nanosecond response time. We are now using TIMELOCK(5,320,640,6000). The trade-off is some additional cpu time and some really good response times. A list of the database was taking about 40-45 minutes (primarily used to force the database into the CF and to make sure all the miscellaneous profile/acid maintenance happens). Now is at 19 minutes .. which is about 130 accessor Ids per second. Rob Schramm (sysprog type back from the land of UNIX) This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- 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
