× 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: Performance question
  • From: booth@xxxxxxxxxxxx
  • Date: Thu, 28 Sep 2000 23:56:15 GMT

Here's the question:  Which is the better way, and why?

I have an RPGLE program that uses embedded SQL to write 80,000 records 
based upon a selection process.   For each of these records we need the 
associated name and zip code added to the record.

Way 1 - Add to the SQL statement by adding in the name file and the fields 
needed and fully populate the file on one pass.

Way 2 - In the same cycle as the embedded SQL, but at the time the record 
is ready to be written, chain to the name file as a separate step and get 
the correct data.

Way 3 - Write two programs.  Use the first program with the embedded SQL 
to refresh the file with selected numbers, then in program 2 just read 
through the unkeyed file and chain the name file, updating the records.

I tried benchmarking Way 1  and Way 2 but system performance was so 
inconsistent that I have no confidence in the results.


_______________________
Booth Martin
Booth@MartinVT.com
http://www.MartinVT.com
_______________________
+---
| 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.