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

>the query still runs, and it appears that it builds the access path more
>quickly than the other way around.  but now I've lost the opnqryf/rpg
>connection.  the rpg is reading the the whole of FILE1, not the subsetted
>records from the opnqryf, even though the override is still in place, and
>i've named my OPNID the same.
>
>any ideas?  Thanks,




Run the job,  and before it starts,  STRDBG on that job.  You don't even
have to give it a program name.   Then,  Look at the SQL Optimizer messages
on in the joblog.  It probably contain this message;

CPI4321
"Access path built for file xxxxxx"

The second level text on that message will tell you why it was building an
index(ie what path you should have out there already).

Other messages will help you too.

Use this command  PRTSQLINF on the CLP program and look at the spool file
created for clues.

John Carr