|
There are a couple of different ways to handle this. One is to check the SQLSTT and then dive into the joblog. STRSQL Record 1 in use by job 888883/ROB/ROBS1. Record 1 in use by job 888883/ROB/ROBS1. Row or object LOCKER in ROB type *FILE in use. It does stop at the locked record and does not continue on. Records up to the locked record will be updated. (Just finished some extensive testing on this.) I did not mess with any isolation clause. The other is to break your set-at-a-time update into a cursor (update where current of cur1). That would give you more granularity, and, could be set up to skip the locked row (or unlock the row by cancelling the locking job) and finish updating the rest. Rob Berendt
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.