|
What is the code after the fetch?? Thanks, Tommy Holden -----Original Message----- From: rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx] On Behalf Of Beeson, Terry Sent: Wednesday, October 19, 2005 10:04 AM To: RPG programming on the AS400 / iSeries Subject: Updatable Cursor "Hangs" on last fetch Hi All I am writing a purge program that deletes most of the records in table HS0101, which has 45 million records. I have defined a cursor as follows C/EXEC SQL Declare CBI Cursor For C+ select <various fields> C+ from HS0101 C+ where AB56TRGDAT >= :fromdate C+ and AB56TRGDAT <= :todate C+ and AB56TRGBA = 'B'and ab56trgact = 'U' C+ For update I ran it over a subset of 4500 records. When it got to the end of the recordset, the FETCH below "hangs". The jobs CPU is increasing but not the IO Count. c/exec sql c+ fetch from CBI into :BIHS0101 c/end-exec If I try this on a much smaller size table with only 100 records and I have no problems. Also if I change the Cursor to be Read Only, again I don't have any problems. This leads me to believe that maybe there's locking issues... or something. The program was compiled with Commitment Control *NONE. Full compile command below CRTSQLRPGI OBJ(TBEESON/CMPHS0101) + SRCFILE(TBEESON/QRPGLESRC) + SRCMBR(CMPHS0101) COMMIT(*NONE) + CLOSQLCSR(*ENDMOD) DLYPRP(*YES) + DBGVIEW(*SOURCE) Any ideas would be appreciated. Regards, Terry -- 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.