No way I know of.
I would imagine that you might want to consider using
journaling/commitment control to rollback the SQL if an error occurs and
would also want to surface the error in the .Net application.
You'll have to make the determination as to whether your business logic
is resilient enough that you can log/ignore the record and move on. A
lot of times you might want to consider rolling back an entire
transaction sequence if something fails.
To track the record lock problem down you might want to write a SP to
call DSPRCDLCK *PRINT to catch the offending program/user right after a
failure. That should help you get closer to the record lock culprit.
Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
-----Original Message-----
------------------------------
message: 3
date: Fri, 22 May 2009 15:26:57 -0400
from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: Anyway to get a .NET ExecuteNonQuery to ignore locked
records?
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
midrange.com
