|
All, Is there a program that will replace the library name within query
definition.
Rich
"Holden Tommy"
<Tommy.Holden@hca
healthcare.com> To
Sent by: "Midrange Systems Technical
midrange-l-bounce Discussion"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
12/21/2006 02:13 Subject
PM RE: How to ID what queries use what
files?
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
I whipped up a little program that will do what is described below & it
will run a FNDSTRPDM on the retrieve source.
Command Source:
http://code.midrange.com/index.php?id=b007531532
Program:
http://code.midrange.com/index.php?id=b50591b20c
Thanks,
Tommy Holden
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
jmmckee@xxxxxxxxxxxxxx
Sent: Thursday, December 21, 2006 12:54 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: How to ID what queries use what files?
Have you looked at RTVQMQRY? On our V5R4 system, the command help
states that
qrydfn source can be retrieved when QMQRY does not exist.
Output would go into a source physical file.
To build the source file, use DSPOBJD to build a list of files.
Then use PDM to locate the files.
I have not done this, but seems like it might work.
John McKee
Quoting GKern@xxxxxxxxxxxxxxxx:
Anyone have any ideas for an automated method of searching queries (*qrydfn objects) to identify what files are used by the query? This is similar to say doing a pdm find-string for a file, but I also
need
to review if there are existing queries that may be impacted by making
a
change to the file. Thanks! Regards, Jerry Gerald Kern - MIS Project Leader Lotus Notes/Domino Administrator IBM Certified RPG IV Developer The Toledo Clinic, Inc. 4235 Secor Road Toledo, OH 43623-4299 Phone 419-479-5535 gkern@xxxxxxxxxxxxxxxx This e-mail message, including any attachments, is for the sole use of
the
intended recipient(s) and may contain confidential and privileged information. Any unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please inform the sender by reply e-mail and destroy this and all copies of this
message.
-- 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-2025 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.