|
Yup. Went through my mind, but escaped before I was able to write it down! :-) -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche Sent: Monday, November 13, 2006 3:13 PM To: RPG programming on the AS400 / iSeries Subject: RE: Record lock checking in RPG or CL? This is a great method, but don't forget when to verify the data has not changed since the first read before doing the update. You didn't have a lock, so another program could have changed the record while your program was waiting on the user. "Turnidge, Dave" <DTurnidge@xxxxxxxxxxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 11/13/2006 03:03 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> cc Subject RE: Record lock checking in RPG or CL? AFIAC - if you are doing that check in CL, it's too late... First of all, you need to do a two-read process. That is, when you initially read the record, you do it without a record lock. When you get to the point you are ready to update (which is the only thing that NEEDS a lock) you read again with the lock, and update the record which releases the lock. The only problem with this method is if ANOTHER program is not set up to do the same thing, and locks the record while the user is at lunch... Dave ________________________________________________________________________ HI, I have a program that I was not concerned of a record lock situation. Now it has happened so I have to put in code to prevent the hanging. Is there any drawbacks to just to do this in the CL, ? TIA, Phil This message contains information proprietary to our company. It is intended to be read only by the individual or entity named above or their designee. Any distribution of this message or the information contained herein without written permission from our company is strictly prohibited. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.