|
It is possible to check for record lock and then retry x number of times or send a message to the job with the lock or after no response, then cancel it. Thanks Tom -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai Sent: Thursday, December 15, 2005 7:34 AM To: RPG programming on the AS400 / iSeries Subject: RE: Updating a Program using SETLL/READPE - Suggestions Ummm. I wonder how you plan to code the sql statement. Declare cursor and fetch each record or just a update statement with where clause? I don't see how the first method would help on speed. The later one is great if you can guarantee no record lock will ever happen. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski Sent: Thursday, December 15, 2005 9:17 AM To: RPG programming on the AS400 / iSeries Subject: RE: Updating a Program using SETLL/READPE - Suggestions Wow, thanks for the great responses, everyone. I'm actually leaning towards moving this code to an SQL statement instead. I already have an index in-place, and I did some basic testing with the SQL interpreter, and it seems to have significantly sped up the process. Again, thanks for the suggestions. Brian.
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.
midrange.com
