RE: join file in query400

Joel,

The most common reason for it to make a copy of the join file is if you specify
sort fields that come from more than one of the underlying physicals.  The
database just can't do that over a join, it needs a single physical, so it makes
a physical copy.

If you want the specific reason for the copy, do a STRDBG before you run it.
You'll get diagnostic messages in your joblog explaining the choices it makes.

As for it being faster in batch, that could be for several reasons, including
all the normal kind of memory pool tuning stuff.  The most likely, though, is
that Query/400 is not real smart.  When it runs interactively, it uses the
equivalent of OPNQRYF OPTIMIZE(*FIRSTIO); when it runs in batch, it uses the
equivalent of OPNQRYF OPTIMIZE(*ALLIO).  Look up the description of this
parameter in the CL Reference for more detail.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

-----Original Message-----
From: Joel Fritz [mailto:JFritz@sharperimage.com]

Sorry, the original message was ambiguous.  I was using a join logical file
in the query.  The thing that made me curious was why Query needed to make a
copy of the join logical file. BTW, it seems to run faster in batch than
interactively.  I tried queries using other join logicals and saw the same
thing.
+---
| 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
+---