Setting LOCK MODE to Wait
Is there a way to influence (force) this setting for the entire online instance? The users are TCP connections using PowerBuilder and they (claim) they can't issue a "SET LOCK MODE TO WAIT" from within theirPowerBuilder programs. I thought that I might try and put this in the informix.rc file, but this appears to be enviroment variables only and I don't see where this setting translates to an environment variable. Is their an onconfig parameter that I'm missing?
I'm really interested in any solution to this, so please answer in this forum rather than private email. TIA, Chris > > Is there a way to influence (force) this setting for the entire online > instance? > > Is their an onconfig parameter that I'm missing?
> I'm really interested in any solution to this, so please > answer in this forum rather than private email. I´m too! I have the same problem with MS Access, MS Query etc. and SQL Retriever 4.17 TIA Reinhard
Well, we had a similar situation with our application. What we did was create a stored procedure that does the SET LOCK MODE TO WAIT and had our application call the stored procedure when it established the initial connection (at login). That should work for an application scenario, but won't be as beneficial to online query tools. HTH, --Steven FProse wrote: > Is there a way to influence (force) this setting for the entire online > instance? > > The users are TCP connections using PowerBuilder and they (claim) they > can't issue a "SET LOCK MODE TO WAIT" from within theirPowerBuilder > programs. > > I thought that I might try and put this in the informix.rc file, but > this appears to be enviroment variables only and I don't see where > this setting translates to an environment variable. > > Is their an onconfig parameter that I'm missing?
Hi! The only thing I was able to locate was the isolation level setup and it is available in PB 5.0. For Infomaker reports I usually set it to dirty read to avoid issues with locked record. Michael Steven Mastandrea wrote: > Well, we had a similar situation with our application. What we did was > create a stored > procedure that does the SET LOCK MODE TO WAIT and had our application call > > the stored procedure when it established the initial connection (at > login). That should > work for an application scenario, but won't be as beneficial to online > query tools. > > HTH, > --Steven > > FProse wrote: > > > Is there a way to influence (force) this setting for the entire online > > instance? > > > > The users are TCP connections using PowerBuilder and they (claim) they > > can't issue a "SET LOCK MODE TO WAIT" from within theirPowerBuilder > > programs. > > > > I thought that I might try and put this in the informix.rc file, but > > this appears to be enviroment variables only and I don't see where > > this setting translates to an environment variable. > > > > Is their an onconfig parameter that I'm missing?
In article <37fcea42.68206555@news.maricopa.gov>, fprose@rocketmail.com (FProse) wrote: > Is there a way to influence (force) this setting for the entire online > instance? > > The users are TCP connections using PowerBuilder and they (claim) they > can't issue a "SET LOCK MODE TO WAIT" from within theirPowerBuilder > programs. > > I thought that I might try and put this in the informix.rc file, but > this appears to be enviroment variables only and I don't see where > this setting translates to an environment variable. > > Is their an onconfig parameter that I'm missing? > > Our PB 6 developers use the following statement in their code - hope it helps. Execute IMMEDIATE "SET LOCK MODE TO WAIT 30" USING SQLCA; Andy Jarman Sent via Deja.com http://www.deja.com/ Before you buy.