|
On your SQL statement when declaring your cursor add the "FOR FETCH ONLY" at the end of the statement Thanks, Tommy Holden -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren Sent: Friday, September 23, 2005 10:15 PM To: RPG programming on the AS400 / iSeries Subject: Re: Record Locking SQLRPGLE You'll want to use "for read only" as part of the sql select (at the end of the statement) and I believe you won't get the record lock. You could also do some searching on "read only" iseries SQL. There are some good articles out there. HTH Pete Helgren Mohammad, Tanveer wrote: >Opps, it seems like SQL lock the record as soon as fetch is performed >Now I need to figure it out how to fetch without locking and using a >STATEMENT. Any quick help will be appreciated. > > > >-----Original Message----- >From: rpg400-l-bounces@xxxxxxxxxxxx >[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mohammad, Tanveer >Sent: Friday, September 23, 2005 4:06 PM >To: RPG programming on the AS400 / iSeries >Subject: Record Locking SQLRPGLE > >I want to read a record and update some values using SQLRPGLE and I >want to make sure that I lock the record before updating it. Just like >CHAIN and UPDATE operation code. Do I have to SET something in >OPTIONS? Also I don't want my files to be journaled to do that. > >Thanks > > > > > > -- 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.