I don't know if it helps, but if the program reads the row for update it will be locked.
From: James H. H. Lampert [mailto:jamesl@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, October 17, 2018 7:03 PM
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Subject: Exclusive locks at the record level?
I've got a project, where I'd like to have a bunch of parallel batch jobs behaving thusly:
All of them are running through the records of a file, in RPG, executing "process x" (involving a single-record web service that takes time to process the record it's fed, apparently well beyond the time needed to transport the data) upon them.
I know we have exclusive locks at the file level, but I can't remember whether or not we have it at the record level, in a form that can be used in RPG, with native record-level access.
It would be nice for each of these parallel jobs to be able to simply grab the next record that isn't already done, and isn't already being processed by a sister job.
Am I making any sense here?
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Exclusive locks at the record level?, (continued)
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.