Re: processing a file

In a message dated 97-07-13 19:25:42 EDT, you write:

> Frankly this surprised me.  I did not expect the three choices to be so
>  close together for time, nor so wide apart on %.

I'm somewhat suprised on the time myself, but perhaps I shouldn't be given
that you were running with nobody else on the system.  I am NOT suprised by
the CPU percentages.  When you take the "K" out of the file spec, you
transfer responsibility for updating your access paths from your program to
the database servers (QDBSRV1 & 2 or something like that).  The percentage is
still taken, it's just not your program taking it.

>  I have figured out that writing out the records selected is what takes the
>  time.  Anyone have any good ideas about speeding up the record writing
>  part?

That's why I push SQL or OPNQRYF.  You don't HAVE to write the records.
 Writing to disk ALWAYS takes longer than reading from it.  On a READ, the
system has to determine where the record is.  On a WRITE, the system has to
determine that there are no duplicates (even if ALWDUP is *NO) and THEN find
an empty space to write it (which takes even longer if reuse deleted records
is set to *YES).

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"The problem with life in the fast lane is that you get to the other end in
an awful hurry." -- John Jensen
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *