|
Reeve Is this embedded SQL? You could use some error handling to start the DELETE after the locked record. The WHENEVER statement lets you continue with the next statement, or go to some label. HTH Vern At 12:17 AM 1/2/03 -0500, you wrote:
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] I'm executing this SQL statement within my RPG program: Delete from TOP001 where TOSTAT = 'RT' TOP001 contains "follow-up" records; they're deleted every morning and new ones are added based on some application logic. When the program runs, it's possible that a user might have a record locked while doing their tracing and follow-up; a locked record tanks the program with an SQL0913 error. Is there a way I can force the set delete to complete in spite of record lock errors (even though such a "capability" is actually undesirable)? The application doesn't care if all the record(s) don't get deleted; they'll be status'ed as closed and deleted the next day. If there's no easy way to make the set delete work, I'll do something else and delete on a record-by-record basis (which will allow me to skip locked records). Thanks, Reeve www.ltl400.com <http://www.ltl400.com/>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.