|
Al
Al Barsa wrote:
In System/38 days, the way to avoid this was to read files opened for read only, without lock, in one program and then lock the records before update and commit in a second program, and this never gave me any performance problems. No longer necessary today.Commitment control is another animal. Updates records remained locked under commitment control until a COMMIT or a ROLLBACK (these are the terms in CL, shorter terms exist in RPG where these are more frequently used) is issued. These performance problems, due to locking, can be major, and are completely controllable with coding style.
Rob
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.