I was thinking that somewhere in the back of my mind. And I got a reply
off-list from someone else who said basically the same thing.
But, basically, if you got this error you'd better notice it quick before
other users start complaining about record locks.
So, we may think that a 1 minute run of a huge batch sql statement isn't
that long and is perfectly acceptable. However if you leave record locks
out there for 1 minute you may hear much wailing and gnashing of teeth
from the users. Then, you have to balance that against running WITH NC.
Isn't there also some limit on how big a commitment chunk (?boundary?) can
This thread ...
Re: Writing from ms SQL to IBM i database (Darryl Freinkel), (continued)
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact