RE: OPNQRYF on a SQL created file

[Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx>]

Hi Chuck,

You got me looking at the override, and our default scope is *ACTGRPDFN, which got me looking a little further and lo' and behold, we changed the calling program from OPM to ILE.  So that was the issue.  We're going to stick with using a logical, but I feel a lot better knowing the issue so in case something similar comes up again, I'm more likely to remember this.

Thanks again to everyone for your input.

-Kurt

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, April 20, 2010 3:37 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: OPNQRYF on a SQL created file

Kurt Anderson wrote:
> Both the old and new version of the PF/Table are not keyed.
> Here's the Override and OpnQryF that was being used.
>
> OVRDBF     FILE(SUMMARYP) SHARE(*YES)                 
> OPNQRYF    FILE((SUMMARYP)) QRYSLT('SUMTYP *EQ "4"') +
>              KEYFLD((PRDLVL) (SVCLVL) (BSLVL))        
>
> The quick fix, for better or worse (better for getting the fix 
> done now, and future understanding; worse for lack of knowing
> what the specific issue was), we created a logical to do what the
> OPNQRYF was doing and changed the program to use the logical.

   By chance were any programs recompiled?  The above shows the 
typical but often incorrect "defaulted" scoping for the override; 
i.e. OVRSCOPE() is unspecified, thus can vary according to the 
parameter default.  Was the incorrect result possibly the result of 
the program reading the actual TABLE rather than reading from the 
shared ODP?  Thus perhaps the incorrect result was not only for 
unordered rows, but also for being inclusive of all rows rather than 
only those rows with selected value for the column SUMTYP?

Regards, Chuck