lock table in exclusive mode

hello all the manual states "This mode denies other processes both read and write access to the table". Does it also affect the dynamic allocating of locks? thanks

I don't understand the question. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Tue, Jan 24, 2012 at 4:32 PM, Tom Lehr <tomcaml@gmail.com> wrote: > hello all > > the manual states "This mode denies other processes both read and > write access to the table". > Does it also affect the dynamic allocating of locks? > > thanks > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >

[Second send; omitted the list first time.] On Tue, Jan 24, 2012 at 13:32, Tom Lehr <tomcaml@gmail.com> wrote: > the manual states "[Lock table in exclusive] mode denies other processes > both read and > > write access to the table". > Does it also affect the dynamic allocating of locks? > If the table is locked exclusively, a single lock does for everything, so you will be less likely to need to dynamically allocate more locks. On the other hand, it reduces concurrency on the table to zero; no-one else can use it while you are using it. -- Jonathan Leffler <jonathan.leffler@gmail.com> #include <disclaimer.h> Guardian of DBD::Informix - v2011.0612 - http://dbi.perl.org "Blessed are we who can laugh at ourselves, for we shall never cease to be amused."

thanks - that is what i was meaning tom