Re: *QRYDFN - details

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

The utility uses some MI functions in RPG to retrieve the filename directly
from the QRYDFN.. These might fail at higher security levels.

Another possibility is to use RUNQRY to print the definition to a spooled
file, CPYSPLF, then read the records that list the files. No security level
problem.

Another way might be to use DMPOBJ, then find the area with the files and
parse it out. Not structured, so a little harder. Contents could be read
into a user space, then processed the same way this utility does it, basically.

The last would be to use RTVQMQRY to get an SQL version of the query, then
parse that for file name and libraries.

At 12:26 PM 8/4/02 +0200, you wrote:
>Hi, Deepak,
>changed this answer to Midrange List as of David's request
>
>Try this link:
>http://archive.midrange.com/repository/extqrydef.htm
>
>It was a good tool in previous releases, but don't know right now, since a few
>weeks ago I read a post from some one reporting it failed in some environment,
>don't remember if it had to do with V. 5.1 and Security level of 40 , or
>something like that.
>Still worth for you to give it try, I think
>Hope this helps, Antonio
>________________________________________________________
>
>Deepak Deshpande escribió:
>
> > I have a small question.
> >
> > When we create a query on a database file with WRKQRY command, it creates
> > an object of type *QRYDFN ...OK......
> > Now I want a CL command which will list down the files used in that query
> > and other details like the library from where the file is picked up etc.
> >
> > Is there any other way of doing it fast?
> > I have hundreds of such (*QRYDFN) objects in my library and I want to know
> > the files used by all these query objects.
> >
> > TIA
> >
> > Deepak Deshpande
> > Analyst-Programmer