|
Still, for performance, what about: H Block(*YES) ... C eval SavedMYKLIST = myklist C myklist setll myfile C read myfile C dow SavedMyKList = MyKList C eval rrn = rrn + 1 C write mysubfile C read myfile C enddo Tests have shown marked improvements in response times by blocking and by avoiding reade --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: RPG programming on the AS400 / iSeries Date: 03/26/04 10:26:43 To: RPG programming on the AS400 / iSeries Subject: RE: RPG400-L Digest, Vol 3, Issue 231 Another example which I think is even more efficient. :) C myklist setll myfile C myklist reade myfile C dow not %eof(myfile) C eval rrn = rrn + 1 C write mysubfile C myklist reade myfile C enddo Rusty -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Marvin Radding Sent: Friday, March 26, 2004 9:58 AM To: rpg400-l@xxxxxxxxxxxx Subject: RE: RPG400-L Digest, Vol 3, Issue 231 While there is nothing wrong with your code, I think this way is more effiecient. C myklist setll myfile C C dou %eof(myfile) C C myklist reade myfile C if %eof(myfile) C iter C endif C C eval rrn = rrn + 1 C write mysubfile C C enddo Marvin Radding message: 1 date: Thu, 25 Mar 2004 14:32:35 -0800 (PST) from: simafrog <SimaFrog@xxxxxxxxxx> subject: SETLL ONE SLIGHT PROBLEM Actually I don't think I can do this here anyway. One problem remaining is that the reade of the Detail file is causing one extra record to be added to the work file, the last one of the batch is duplicated. Here is the code: C BLD BEGSR C* C OHKEY SETLLORDHEDR 40 C* C *IN40 DOWEQ*OFF C* C OHKEY READEORDHEDR 40 C *IN40 IFEQ '0' C* C C* C ODKEY SETLLORDDTL 50 C *IN50 DOUEQ*ON C ODKEY READEORDDTL 50 C WRITEORDSWRKF C END C END C END C* C ENDSR
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.