× 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: Accessing files In QTEMP
  • From: Evan Harris <spanner@xxxxxxxxxx>
  • Date: Thu, 19 Oct 2000 08:04:10 +1300

Dan,

> >It can cause more problems that its worth.<
>How?  Yes, there's more cleanup involved, but that is hardly a daunting task.

I have a number of multi member file that were created by developers. No 
clean up routines, no housekeeping, no management.

These files regularly have to have housekeeping performed just so they 
don't reach the 32,767 limit. Everything (processing wise) pretty much 
stops if this happens.

In my opinion, these files create more problems than they are worth, 
because the developers didn't take the time to solve the problem properly.

Any strategy that doesn't solve/perform it's own housekeeping or relies on 
"other" tasks to run regularly is doomed to failure.

I think the solutions that presented a master file with some kind of key 
for the temporary data, or the use of QTEMP and rolling the whole job into 
one chunk of code sound more like the way to go to me.

Just my particular take on this.

Regards
Evan Harris

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