Not calling CLOSE when finished.

I'm maintaining some informix C code and have noticed that there are a lot of places where the programmer didn't call a CLOSE after he/she was done with the cursor. The next time the routine is called I assume that Informix does the close first and then the open as coded, however I'm wondering what the impact to system performance is with so many open cursors out there. In time I will fix all of the missing closes but we're kinda frozen till fall ( after peak load ) and it doesn't qualify as an emergency since the code works. Sooo, with say 100 or so extra cursors hanging around open is there any performance to be gained by closing them? thanks in advance, bob maccione bmaccion@promus.com ps: hi naomi, it's raining again...