RE: opnqryf question - opnid, joins, overides, etc.

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Richard - when I said "MUST" below, I didn't mean that you would get an
error - sorry about that.

I meant that in my experience, if the first KEYFLD field is not from the
first file, it forces OPNQRYF to read each record from the second file.  And
then it takes forever.  Ive never seen this in writing, I made a note in my
book that OPNQRYF behaves this way.

I think you should put *JOB in the scope of both the OVRDBF and the OPNQRYF
- that is probably why OPNQRYF is reading all the records in the file.  The
OPNQRYF is no longer active by the time RPG gets it.

Also, use CPYFRMQRYF instead of RPG for debugging this problem - that will
isolate the OPNQRYF and eliminate the RPG pgm to find the problem!


-----Original Message-----
From: Richard B Baird [mailto:rbaird@esourceconsulting.com]
Sent: Tuesday, February 05, 2002 7:27 AM
To: midrange-l@midrange.com
Subject: RE: opnqryf question - opnid, joins, overides, etc.



>The first KEYFLD _MUST_ be from the first file in the OPNQRYF.  When you
>switch SELCOPY to the first file, add a new KEYFLD from SELCOPY to the
front
>of the KEYFLD list.

This, I didn't know.  Which makes me wonder why I didn't get a runtime
error when I executed the opnqryf.   I'm sure the first keyfld wasn't from
the primary file.