|
There is a way to do this, with a little work. The RVQMQRY command will extract the query definition to a source file, which you could then scan. Just be sure to specify ALWQRYDFN(*YES). To do this to a bunch of queries you would have to write a C/L program which processes a file created with the DSPOBJD command. This will only help you find them. They still have to be recreated manually. The System/38 had a command to create queries, but the AS/400 doesn't for some reason. > -----Original Message----- > From: Leland, David [SMTP:dleland@Harter.com] > Sent: Friday, February 25, 2000 5:38 AM > To: 'RPG400-L@midrange.com' > Subject: RE: Query/400 to RPG program > > The one thing I hate about queries is something that was brought up in a > previous post. If I make a change to a database file, I can very easily > compile all RPG programs which reference the file (I use FNDSTRPDM w/ > OPTION(*CMPL) quite a bit). But, I can't w/ Queries. I have to manually > go into each one. And there isn't a good way to determine which queries > use the affected file. For companies which make a lot of database changes > (our's is one), I strongly discourage Queries. > > Dave > > -----Original Message----- > From: Rob Berendt [ <mailto:rob@dekko.com>] > Sent: Friday, February 25, 2000 7:20 AM > To: RPG400-L@midrange.com > Subject: Re: Query/400 to RPG program > > > What is so bad about Query? Is this some sort of programmers union > uprising? 'The users are access their own data without going through > us! Wait, lets remove the easy maintainability of Query and put it into > RPG!' > > > > > > danielh@elp.rr.com on 02/25/2000 02:23:59 AM > Please respond to RPG400-L@midrange.com@Internet > To: RPG400-L@midrange.com@Internet > cc: > Fax to: > Subject: Query/400 to RPG program > > I just started working with RPG. This company lives on querys! They run > around a 80 different ones a day. Is there a good tool that anyone would > suggest that would convert querys to code. we run 3.7. > > Thank you > Dan > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.