|
Not sure exactly why the SQL update would affect the locked record status maybe an IBMer will chime in. But Select statements will NOT affect this, it's simply because when the SQL update ran it would lock, update (which releases the lock). But I'm not sure that this *should* have affected the record locked by the RPG read statement. It could be a bug but like I said until IBM chimes in I am reluctant to think it's a bug just a little known fact. Thanks, Tommy Holden -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz Sent: Friday, June 02, 2006 11:52 AM To: RPG programming on the AS400 / iSeries Subject: Re: Update Operation Failure Help Please So do we know know an sql update between a native read & update is a problem? What if the sql had been a select statement, I assume would we no longer be on the correct record to update... Is this like a shared odp? jim ----- Original Message ----- From: "Brian Piotrowski" <bpiotrowski@xxxxxxxxxxxxxxx> To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> Sent: Friday, June 02, 2006 12:17 PM Subject: RE: Update Operation Failure Help Please
Thanks, Tommy. That worked great. I moved a bit of code around so
that
my subsequent SQL statements occur after the update. Brian. -----Original Message----- From: Holden Tommy [mailto:Tommy.Holden@xxxxxxxxxxxxxxxxx] Sent: Friday, June 02, 2006 11:57 AM To: RPG programming on the AS400 / iSeries Subject: RE: Update Operation Failure Help Please Geez...not an answer to your question directly but this is really ugly...why not just use native I/O on the ssw85 file updates(which incidentally could be causing your issue but I'm not sure on that...) SQL IS a wonderful thing but use it where needed, not just because
it's
there...not to mention it will run a lot faster since you're doing 1
I/O
compare to 3. -- 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.