Re: OPNQRYF looks good, bad results

[Brian Johnson <brian.johnson.mn@xxxxxxxxx>]

On Mon, Mar 30, 2009 at 2:46 PM, Dan Rasch <drasch27@xxxxxxxxxxx> wrote:

> I run the OVRDBF, and it looks fine:
> OVRDBF FILE(POMST) SHARE(*YES)
>
> Then, I run one of the four OVRDBF's.  Here's one example:
>
> OPNQRYF FILE(POMST) OPTION(*ALL) +
> QRYSLT('(POMSTS = ''0'') *AND (POMCPY = 01 )') +
> KEYFLD((POMLOC) (POMVNM) (POMVCD) (POMPON))  +
> OPTIMIZE(*FIRSTIO) SEQONLY(*YES 10)
>
> It runs with no error, and I am expecting to read the file by:
>   location, vendor name, vendor code, and PO#
> (as coded).  What I get is by PO#.
>
> Any ideas?
Have you looked at the scope of the override?  This aspect can be tricky
because the default for scope varies  depending on activation group.