|
Good question - I sought an answer!! Created a query called VERN/TEST that had file VERN/JOBLOG in the definition. Created this program VERN/TESTRUNQRY PGM RUNQRY QRY(VERN/TEST) RUNQRY QRY(VERN/TEST) QRYFILE((VHCURLIB/JOBLOG2)) ENDPGM Ran DSPPGMREF and got the following: 3/16/07 Display Program References DSPPGMREF Command Input Program . . . . . . . . . . . . . . . . . . : TESTRUNQRY Library . . . . . . . . . . . . . . . . . : VERN Output . . . . . . . . . . . . . . . . . . : * Object types . . . . . . . . . . . . . . . : *PGM Program . . . . . . . . . . . . . . . . . . . : TESTRUNQRY Library . . . . . . . . . . . . . . . . . . : VERN Text 'description'. . . . . . . . . . . . . : Number of objects referenced . . . . . . . : 4 Object . . . . . . . . . . . . . . . . . . : *RUNOPT Library . . . . . . . . . . . . . . . . . : *RUNOPT Object type . . . . . . . . . . . . . . . : *FILE File name in program . . . . . . . . . . : *RUNOPT File usage . . . . . . . . . . . . . . . : Output plus 3 references to IBM service programs. FYI Vern At 10:01 AM 3/24/2007, you wrote:
If a RUNQRY is in a CL, then shouldn't that compiled CL show up in the GO CMDREF?Substitution variables can be used all over the place, what I call soft coding.>One problem with QRYDFNs is that RUNQRY can be set to point to files >that are completely different from those in the definition - of >course, the company that I saw doing this was IBM itself, in iDoctor. > >And then there are QMQRYs that use substitution variables for the >file name - Oy! > >Hope this does not confuse too much - heh! > >Vern > >At 03:34 PM 3/22/2007, you wrote: > > >Nick, > > > >To find out which files are used with queries you can convert QRYDFN > >objects to QMQRY sources with the RTVQMQRY QRYDFN(*YES) into a SRCPF. > > > > >From there you can use FNDSTRPDM or SQL to scan the sources. > > > >Regards, > >Carel Teijgeler > > > >*********** REPLY SEPARATOR *********** > > > >On 22-3-2007 at 12:34 Nick_Radich@xxxxxxxxxxxxxx wrote: > > > > >Hi Mark, > > >> > >Yup, I was looking into that for the Querys if I had to "Roll My Own". In> >the far distant past, I have pretty much written my own at various client> > >sites, using DSPPGMREF and DSPDBR. Along with using Pathfinder and other> >tools that were available at those sites. > > > > > >"Mark S. Waterbury" <mark.s.waterbury@xxxxxxx> > > >Sent by: midrange-l-bounces@xxxxxxxxxxxx > > >03/22/07 12:20 PM > > >Please respond to > > >Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > > > >To > > >Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > >cc > > > > > >Subject > > >Re: Finding an object's usage > > > > > >Hi, Nick: > > > > > >See: > > > > > >http://www.systeminetwork.com/isnetforums/archive/index.php?t-23052.html > > > > > >for info.about a published article and tool called RTVQRYF that includes > >DSPQRYD and DSPQRYF ... this may help you for the *QRYDFNs (Query/400 > > >queries). > > > > > >As others have mentioned, DSPPGMREF to an *OUTFILE will provide info on > >what *PGMs use which *FILEs. DSPDBR to an *OUTFILE will provide > > >cross-references such as LFs-to-PFs. What else did you need? > > >> > > >> > > >> "rick baird" <rick.baird@xxxxxxxxx> > > >> Sent by: midrange-l-bounces@xxxxxxxxxxxx > > >> 03/22/07 11:59 AM > > >> Please respond to > > >> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > >> > > >> To > > >> "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > > >> cc > > >> > > >> Subject > > >> Re: Finding an object's usage > > >> > > >> no single command (unless you own hawkeye's pathfinder) > > >>> > >> DSPPGMREF *ALL will get all program references, but you'll have to look> >for queries and other stuff another way. > > >> > > >>> Hello everyone, > > >>> > > >>> Is there a Command I can run, or a system file I can query, that will > >show me all of the objects on my system that reference a particular file? > > > > > >--> >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list> >To post a message email: MIDRANGE-L@xxxxxxxxxxxx > >To subscribe, unsubscribe, or change list options, > >visit: http://lists.midrange.com/mailman/listinfo/midrange-l > >or email: MIDRANGE-L-request@xxxxxxxxxxxx > >Before posting, please take a moment to review the archives > >at http://archive.midrange.com/midrange-l. > >-- >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/midrange-l >or email: MIDRANGE-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.