RE: qry and dsppgmref

Chuck,

Yes, you are correct. I do remember reading it in the memo to users
when 6.1 first came out (which is now almost 3 years ago, for those still on
V5R4...hint hint start looking at what needs to be done to upgrade your OS),
but you have to resave the query on 6.1 for this to work. I wrote an
article on this in my monthly iTech Solutions Newsletter in March 2010. The
link to the article is http://www.itechsol.com/newsletters/2010-03.html

This is another great feature of 6.1.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn: http://www.linkedin.com/groups?gid=2206093

iTech Solutions because IBM i (AS/400s) didn't come with System
Administrators



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, January 26, 2011 7:04 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: qry and dsppgmref

On 1/26/11 6:24 AM, David FOXWELL wrote:

I thought that at V6.1 DSPPGMREF on a program would show all the QRY
executed by that program. ?

What IBM i 6.1 provided additionally for the DSPPGMREF was to name a
*QRYDFN [Query/400 Query Definition] object or a generic [name] on the
PGM() parameter, for which by specification also of either the
OBJTYPE(*ALL) or OBJTYPE(*QRYDFN [...]), the *FILE objects that the
query or queries reference(s) will be included in the output of the
request [but only if the *QRYDFN has been updated or created on\since v6r1].

Note: Because the special value *ALL for object type now includes
that additional object type, generic names used for the PGM() parameter
on previously coded DSPPGMREF OBJTYPE(*ALL) may see slower response and
more records of output, as compared to when run on a prior release; to
avoid the effect for when information about *QRYDFN is not desired, code
explicitly which object types for which references should be extracted.
The support and its possible impact to performance were to have been
documented in the v6r1 MTU [Memo To Users]; I did not verify presently,
but recall it was there, possibly even with a description of some means
to update existing query objects to have the "where used" information
added, without having to 2=Change and 1=Save from the interactive WRKQRY
utility.

Regards, Chuck