|
So, if you're changing all your queries form Lib A to Lib B, you still have to do this manually? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz Sent: Monday, June 12, 2006 10:29 AM To: Midrange Systems Technical Discussion Subject: Re: BIG Query Question This clp creates, in each library in your library list, a source file called QRTVQRY, each member in the source file is the name of a query object type *qrydfn (which is what WRKQRY creates). In that source member you will see the files and fields used. It is basically a sql source with some other codes related to wrkqry. This is a sample source member: H QM4 05 Q 01 E V W E R 01 03 06/06/12 05:32 V 1001 050 V 5001 004 *HEX SELECT ALL COCONO, CODIV, COLOC, COIDNT, CODS40, CODS07, COAPLC, COGRCD FROM ABCLIB/CONAME T01 WHERE COCONO = 02 AND CODIV = 010 AND COLOC = 10 ORDER BY COCONO ASC, CODIV ASC, COLOC ASC jim franz ----- Original Message ----- From: "John Candidi" <jacandidi@xxxxxxxxxxxxxxxxxxxx> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> Sent: Monday, June 12, 2006 10:56 AM Subject: RE: BIG Query Question
What exactly does this do and does this work on queries created using just the WRKQRY command? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz Sent: Monday, June 12, 2006 9:50 AM To: Midrange Systems Technical Discussion Subject: Re: BIG Query Question what a difference a comma makes..<grin> this is prob 10 years old.. PGM /* rtv qm qry source for all queries in + production libraries */ DCL VAR(&MSG) TYPE(*CHAR) LEN(70) DCLF FILE(QADSPOBJ) MONMSG MSGID(CPF0000) /* global monitor */ /* DELETE ALL THE QRTVQRY SOURCE FILES TO BUILD AGAIN */ $DELT: DLTF FILE(*USRLIBL/QRTVQRY) MONMSG MSGID(CPF2105) EXEC(GOTO CMDLBL($NEXT)) GOTO CMDLBL($DELT) $NEXT: DSPOBJD OBJ(*USRLIBL/*ALL) OBJTYPE(*QRYDFN) + OUTPUT(*OUTFILE) OUTFILE(QTEMP/ZDSPOBJD) + OUTMBR(*FIRST *REPLACE) OVRDBF FILE(QADSPOBJ) TOFILE(QTEMP/ZDSPOBJD) $READ: RCVF MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL($END)) /* IF A QRY, RTV SOURCE */ IF COND(&ODOBTP *EQ '*QRYDFN') THEN(DO) /* IF NOT A SOURCE PF , CREATE IT */ CHKOBJ OBJ(&ODLBNM/QRTVQRY) OBJTYPE(*FILE) MONMSG MSGID(CPF9801) EXEC(DO) CRTSRCPF FILE(&ODLBNM/QRTVQRY) TEXT('RTVQMQRY src') + AUT(*ALL) ENDDO RTVQMQRY QMQRY(&ODLBNM/&ODOBNM) + SRCFILE(&ODLBNM/QRTVQRY) SRCMBR(*QMQRY) + ALWQRYDFN(*YES) ENDDO GOTO CMDLBL($READ) $END: ENDPGM You can scan these source members like any other source files. jim franz ----- Original Message ----- From: "Michael Ryan" <michaelrtr@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Monday, June 12, 2006 10:29 AM Subject: Re: BIG Query QuestionWow...no one has ever called me Sweet Michael...<pout> On 6/12/06, Chuck Lewis <chuck.lewis@xxxxxxxxxxxxx> wrote:Sweet Jim, At least I can pull together a list of files used in what queries and if they can tell us what files are changing, we can just concentrate on those. Better than redoing ALL of them :-) But you do REALLY WISH IBM would come up with some way of doing this... Thanks ! Chuck -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz Sent: Monday, June 12, 2006 9:56 AM To: Midrange Systems Technical Discussion Subject: Re: BIG Query Question I have asked same question several times over many years and not got an answer that such an api exists. Would be great if it does, but I have to deal with this over many times. I do have a way to identify which files and fields in use by a query (thru rtvqmqry cmd you can create a source mbr of a *qrydfn qry) jim franz -- 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. -- 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.