Re: RPGLE SETLL / READE for update getting record lock on different key (private reply) -- RPG400-L

Subject: Re: RPGLE SETLL / READE for update getting record lock on different key (private reply)
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Fri, 26 Oct 2018 12:02:56 -0400
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 2018-10-26 11:40 AM, Mohammad Tanveer wrote:

This situation happens once in a while.. I am recommending to change record
wait time from 60 to 120 seconds ... hopefully this will resolve the
issue...

Instead of letting the error go to MSGW, you could add some exception-handling to your program so you could do the retry in the program itself.

ok = *off;
dow not ok;
monitor;
reade(e) key file;
ok = *on;
on-error 1218: // record lock
// try again
endmon;
enddo;

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: RPGLE SETLL / READE for update getting record lock on different key (private reply) , Birgitta Hauser
Re: RPGLE SETLL / READE for update getting record lock on different key (private reply) , Mohammad Tanveer

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.