× 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 loading a subfile
  • From: jpcarr@xxxxxxxxxxxx
  • Date: Wed, 13 Sep 2000 11:19:53 -0400



James kilgore said;
>Booth
>Just thinking out loud, never tried this: Have your selection process
performed
>by a program other than your display program.  Have the two communicate
via data
>queue.  As the display program receives qualified records from the data
queue
>perform your WRITE of the subfile.  And a WRITE to the display so the user
can
>see them. Each time a new record comes in, do a READ/READC of the subfile
to see
>if the user has made a selection.
>
>If they have, process their selection, then play catch-up from the data
queue
>before you redisplay the subfile.


James
I do this session at COMMON.   Externalizing your I/O with SQL.   I use an
external routine using SQL.  It does the Prepare and Fetches,  and passes
the results back as a parm to the caller.  The caller just formats the
Where and Order By clauses.

It works great for Multi-Row Fetches (10-20 records at a time passed back
via a Multi-occurring D/S)

Very slick, and fast.

John Carr




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