RE: Quick field scan

[John P Carr <jpcarr@xxxxxxxxxxxx>]

        Sorry that should have been ....


                If you use an imbeded SQL program that did the SQL LIKE
keyword,
        OS/400   would NOT    have to move the record from the ODP 
                to the RPG input field Buffer,  etc, look at the record,
say,  Nah,
        and do the same thing over.

                The interagation would be done at a much lower leve.

                The same thing could be done with OPNQRYF command with the
*CT
        function(Contains).

                John Carr






                From:   Bob Cozzi@cozzi on 07/19/99 06:05 PM
                To:     MIDRANGE-L@MIDRANGE-L@midrange.com@SMTP@EXCHCONNECT
                cc:      

                Subject:        RE: Quick field scan

                Here's a suggestion:

                 1. Create a logical view containing only the field in
question.
                 2. Override the database file (logical view) so that
NBRRCDS( ) =
        number of
                records in the file.
                 3. Override the SEQONLY parm to *YES with the number of
records =
        to some
                large number.
                 4. Read the record.
                 5. SCAN the record (I'm assuming you're using RPGIII) for
your
        data.

                This could increase throughput.

                Bob Cozzi

                http://www.RPGIV.com




                > -----Original Message-----
                > From: owner-midrange-l@midrange.com
                > [mailto:owner-midrange-l@midrange.com]On Behalf Of Gerald
Magnuson
                > Sent: Monday, July 19, 1999 4:11 PM
                > To: MIDRANGE-L@midrange.com
                > Subject: Quick field scan
                >
                >
                > I need to provide a method to scan for a character string
                > contained anywhere within a field 25 characters long..
                > The user wants this to be an INTERACTIVE process.
                >
                > the file contains around 75k to 100k records.
                >
                > I have a rpg program that uses the scan op code within a
do loop.
                >
                > I run this program interactivelyand I get my results in
about
                >  3 minutes (48cpw).
                > I say "Sorry, we are not going to eat up that many cycles
for
                > this interactivly, we will run this in batch."
                >
                > So my user asks:  "Well then, why is it that I can look at
a
                > report in my outq with all the data (1400 pages) and scan
                > and find the data in 30 to 50 seconds, and It takes you 3
                > minutes?"
                >
                > I know that there is something about spool files that
makes
                > this type of scanning much faster.
                >
                > so the questions are:
                >     Is there a method to perform this type of scan
interactivly?
                >         (by interactive I mean, to go through 75k records
in 30 to
                >          50 seconds)
                >
                >     What is the reason that the spool file find is so much
faster?
                >
                >
                > Thank you...
                >
                >
                > +---
                > | This is the Midrange System Mailing List!
                > | To submit a new message, send your mail to
        MIDRANGE-L@midrange.com.
                > | To subscribe to this list send email to
        MIDRANGE-L-SUB@midrange.com.
                > | To unsubscribe from this list send email to
                > MIDRANGE-L-UNSUB@midrange.com.
                > | Questions should be directed to the list owner/operator:
                > david@midrange.com
                > +---
                >

                +---
                | This is the Midrange System Mailing List!
                | To submit a new message, send your mail to
        MIDRANGE-L@midrange.com.
                | To subscribe to this list send email to
        MIDRANGE-L-SUB@midrange.com.
                | To unsubscribe from this list send email to
        MIDRANGE-L-UNSUB@midrange.com.
                | Questions should be directed to the list owner/operator:
        david@midrange.com
                +---



        +---
        | This is the Midrange System Mailing List!
        | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
        | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
        | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
        | Questions should be directed to the list owner/operator:
david@midrange.com
        +---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---