Clifton Oliver <[EMAIL PROTECTED]> wrote on 09/01/2005 10:31:10 AM: > Your named COMMON "trick", especially with the "second step" of > avoiding the file reopen is not a work-around. It is considered by > most to be the "correct" way to code one of these subroutines.
I agree with Clif - I've seen this approach make a huge difference many times. Don't consider it a work-around, but rather embrace this approach throughout the application. That being said, the original question is why this particular query became an issue all of a sudden. Although UniVerse hasn't been upgraded on this box recently, *something* has clearly changed. Maybe one of the impacted files has dramatically outgrown its configured size. Maybe somebody performed a uvregen that changed the size of the rotating file pool or something else. Maybe the user load has changed recently. Maybe a file design has been changed. Maybe something else has changed in the application environment, such as installing an application modification that is consuming disk or memory resources. Maybe there's a problem with some component of the disk subsystem. The list of possible causes is long; whatever changed may not have directly caused the problem with your query, but it may have been enough to cause a bottleneck in some system resource. What is the operating system being used? Is it possible that something changed there? Was any performance monitoring done at the O/S level while the problem was occurring? That would provide some valuable clues. Bottom line - sorry, no easy answers. ;-) Tim Snyder Consulting I/T Specialist , U2 Professional Services North American Lab Services DB2 Information Management, IBM Software Group ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
