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



Thanks,

I'm going to use a combination of these two solutions.

I'm adding a second program that will read the masterfile again sorted on the library name and access the detail files. That lets me close the files after each library has been treated.

-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Adam Glauser
Envoyé : mercredi 14 janvier 2009 17:45
À : rpg400-l@xxxxxxxxxxxx
Objet : Re: Problem with duplicated file names

Carel Teijgeler wrote:
3) If the library name from the master PF changes, then clode the
detail PF and return to step 2.

No clutter of numerous renames, subprocedures, etc.

The OP specifically said he does not want to close these files between reads. Personally, I like EXTFILE() + USROPN() method too, but I can see where it could cause a fairly significant performance hit if this routine is called frequently and the library changes on most calls.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.