× 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: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Thu, 27 Jan 2000 16:08:21 -0500

Bruce,

Why do you think there would be a difference?  The only difference I've ever
seen is functional - members of source files have maintainable attributes,
whereas data files do not.  I know of no reason why performance would be any
different between a source file and a data file with the same 3 fields and
record length.  RPG programs certainly don't know the difference between them.

Dave Shaw

-----Original Message-----
From: Bruce Jin [mailto:brucej@mrc-productivity.com]

 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.
+---
| 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.