Re: QMQRY and OVRDBF - has senility set in?

[CRPence <CRPbottle@xxxxxxxxx>]

  What is the actual message & text?  Is the SQL message logged too? 
Retrieve the source from the query and include that in your message, 
along with the OVRDBF issued [irrespective of scope], to correlate to 
the error details.

  Overrides only [effectively] apply to /open/ functions; e.g. the file 
named in the FROM clause of a SELECT statement should honor a *CALLLVL 
scoped override to a named TOFILE().

Regards, Chuck

Reger, Bill wrote:
> I have a QMQRY that has a file name in it to operate upon.  The file
> name inside the QMQRY is not qualified by a library name, so it would
> be using the *LIBL normally.  When I do an OVRDBF to point the file
> name at a specific LIBRARY, the QMQRY fails and tells me "File name
> in *LIBL type *FILE not found".
>
> Well yeah, I know.  That's the reason I'm doing the OVRDBF.  I know I
> can change the QMQRY to accept a Library VARiable.  But I'd really
> like to see if the OVRDBF can handle this for me.
>
> I would swear I've seen this work before.  And I've also tried every 
> combination of OVRSCOPE parameters that are available.  Still no
> good.
>
> Am I just getting senile?  (Please tell me no!)