|
Interesting idea. Only problem is that 32766 row limitation. I
guess
that boils down to the "I know it will never exceed..." Murphyisim.
And
it may never will for your application.
Yea, I do not know why when IBM went to RPG IV, they put a max of 32766 on rows. If you could use real array you could go to 65763 but the IBM pre-complier is still RPG III based so who knows how long that will be. I am hoping that they are in the process of rewriting it. But, of course, the other issue is you only have 16MB total storage available but in practice, to need to read in more than 32766 records would seem unreal. That would say they is something wrong with the SQL. If one did have an issue like that, you could run a count and if over 32766, revert to a regular loop or read in 32766 and then read the next block although I am not sure about positioning back to the next record.
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.
midrange.com
