|
All,
We've got a .NET application that updates a records in a table on the iSeries.
Sometimes, it runs into a locked record and aborts.
Is there anyway to get it to ignore the locked records?
I'm thinking the best we could do would be to capture the eexception
and go on to the next statement, which would be any records that would
have been processed after the locked records will be skipped also.
I was thinking a continue handler in a SQL stored procedure would
help....but it apparently handler CONTINUEs with the next statement
and not any other records affected by the statement that had the
problem. So the effect would be the same.
Note I am trying to track down the application on the iSeries that
aren't committing changes in a timely manner, but it's not easy.
Charles
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
