Re: QMQRY and OVRDBF - has senility set in?

[CRPence <CRPbottle@xxxxxxxxx>]

  The LABEL ON is an example where an override will not assist, 
[effectively] because, it is not an open.  There is no DDL statement 
[except for any DML statement within] that is influenced by an override 
AFaIK.  The library name will need to be a variable to be passed when, 
or the library list managed before, the QM query request is performed.

Regards, Chuck

Reger, Bill wrote:
> "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()."
>
> Perhaps this is why I'm so sure I've seen this work before.
> I'm not doing a SELECT statement. This time my QMQRY is doing a
> "LABEL ON" SQL statement - trying to update the Field Text/Column
> Headings. Here is the pertinent stuff:
>
> The QMQRY SQL "LABEL ON" operation:
>
> LABEL ON "filename"
> ("FIELD1" IS   'Field               Number              One', 
>  "FIELD2" IS   'Field               Number              Two' )
>
> The commands entered and the resulting JOBLOG:
>
> 4 > OVRDBF FILE(filename) TOFILE(datalibr/filename) SECURE(*YES)
> OVRSCOPE(*CALLLVL)
> 4 > strqmqry QMQRY(objlibr/qmqryobj)
>     filename in *LIBL type *FILE not found.
>     RUN QUERY command failed with SQLCODE -204.
>     RUN QUERY command ended due to error.
>     STRQMQRY command failed.