× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Performance issue: open/read PF vs open/read SRCPF
  • From: "Martin, Booth" <BoothM@xxxxxxxxxxx>
  • Date: Thu, 27 Jan 2000 16:32:33 -0500

If performance on 500 records is an issue then perhaps you are really doing
more than a simple reading-through of the 500-record file?  

Why not define a 500 element array? (if two fields, use an alternating array
for Field2.)  Then, load your array(s) in the *INZSR and be done with it for
the life of the session; no more opening and closings.  Performance from the
array(s) should be lightening fast.



-----Original Message-----
From: Bruce Jin [mailto:brucej@mrc-productivity.com]
Sent: Thursday, January 27, 2000 2:35 PM
To: boothm@goddard.edu
Subject: Performance issue: open/read PF vs open/read SRCPF


 I wonder how much difference there is (in terms of performance) when I use
a physical file versus a source physical file. Assume I do OVRDBF, OPEN,
READ, CLOSE in RPG. The record lengths for both PF and SRCPF are the same.
The PF has only 1 or 2 fields in it. Both PF and SRCPF have 500 records.

Thanks
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.