× 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: Jim Langston <jlangston@xxxxxxxxxxxxxxxx>
  • Date: Thu, 27 Jan 2000 13:34:02 -0800
  • Organization: Conex Global Logistics Services, Inc.

As far as I am aware, there should be 0% performance difference.
As far as your RPG program knows, it's a physical file.  I don't think
it can tell the difference between a PF-SRC and a PF-DTA, that is
just an attribute byte that is used by programs to know how to open
the file.

That is, PDM will not allow option 2 (change) on a member of a
PF-SRC, but will allow you to a PF-DTA.  Also, PF-SRC doesn't
allow you specify the DDS for the file on creation.

Regards,

Jim Langston

Bruce Jin wrote:

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

Replies:

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.