|
Hi All Thought I would provide an update. The problem was down to the Indexes. The program was using arrival sequence. Still don't know why changing the Cursor from Read-Only to Update caused it to change the access path though. Thanks for your help. Regards, Terry -----Original Message----- From: rpg400-l-bounces+terry.beeson=henryschein.co.uk@xxxxxxxxxxxx [mailto:rpg400-l-bounces+terry.beeson=henryschein.co.uk@xxxxxxxxxxxx] On Behalf Of Beeson, Terry Sent: 20 October 2005 09:23 To: RPG programming on the AS400 / iSeries Subject: RE: Updatable Cursor "Hangs" on last fetch Thanks for the suggestion. That was one of my options, and maybe I'll end up doing it this way. My question is: why does changing the cursor from "read-only" to "updatable" cause the last fetch (which should return "no more records") to take so long. I know the last Fetch will finish. It finishes processing the recordset quite quickly, and then it appears to scan through to the end of the file (45 million records). However DBMON shows absolutely nothing on this fetch. I change the cursor to Read-Only and the last fetch finishes instantly. Why?? Any ideas? Regards, Terry
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.