Re: WRKQRY output files: how to determine w/o using WRKQRY

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

GA

You still might be out of luck - RUNQRY lets you change the output type, as 
well as the query files from which the data comes. You can also choose 
between detail and summary at runtime. So your query could be defined for 
whatever but you can direct it to a PF and make other changes in how it looks.

Ergo, there may be no way to track down how it got there.

A feature, not a bug. You can hide all kinds of things this way.  ;-)

HTH - but it probably won't
Vern

At 04:06 PM 6/10/2004, you wrote:
> I've got a data file with externally described fields that I cannot
> determine where or how it was created.  DSPOBJD *SERVICE shows blanks for
> the source information.  I already did a DSPPGMREF *ALL/*ALL to an
> outfile, and there's nothing showing that creates the file.
>
> Since this file has 'QRY' at the end of its name, I'm guessing that it was
> created by a query (duh), but I've not found any queries that come close
> to the name of the file.  There are hundreds of queries on our system.
>
> Tried RTVQMQRY on all of these queries and scanned for the file name, but
> information on the query output is NOT included in the QMQRY source.  (I
> tested this with a query I knew outputs to a data file.)
>
> I was hoping to find some API or other utility that would pull this
> information out of the *QRYDFN objects.  Anybody know?
>
> TIA, GA