RE: sysprocplan Locking?

Neil, > Under what conditions might sysprocplan get locked? What version of which engine are you running? > We have a problem on one program which is used by man users and > we tracked the concurrency problem to a lock on sysprocplan. > Where do we start looking? Depending upon your version, I'd say stop looking. You've found the bug. As I remember the problem, it went like this. You have a procedure named myproc(). When the first user executed myproc() he placed a lock on it in sysprocplan. No other user was then able to execute myproc() because of the lock. The situation continued until (and this is where it gets fuzzy), the first user ended his session. That's the way I remember it, but it doesn't make sense. Perhaps it was only locked for the duration of the first user's transaction. That makes more sense but it isn't the way I remember it. Let me know your version/platform info. I'll try to look up the bug and see when it was fixed. That may take a couple of hours though, since I'll need to use a modem. --Craig (craig@chemistry.utah.edu)