× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Vern,

I believe others have used the dump approach before, but you still have the problem that IBM does not document the layout of the *QRYDFN. It would be better to get to V6R1 and use the supported DSPPGMREF interface.

If memory serves me right, any *QRYDFN built on a V6R1 system should support DSPPGMREF. And there were going to be PTFs provided for V6R1 to scan existing (migrated) *QRYDFNs and provide the necessary updates so that pre-V6R1 *QRYDFNs could also be supported by DSPPGMREF (without having to rebuild the *QRYDFN).

Bruce


Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:
Bruce

Can a person use the output of DMPOBJ and get the same information as
resolving to the *QRYDFN does? Yeah, it's ugly and all, just wondering.

Vern

Bruce Vining wrote:
Not a list of queries that have output files, but in V6R1 DSPPGMREF has been enhanced to support the display and print of file usage within a *QRYDFN. This might do the trick.

There doesn't seem to be a lot of information available, but if you google V6R1 QRYDFN you'll find hits in a V6R1 DB2 Technical Overview and also in the V6R1 Memo to Users.

Bruce

Frances Denoncourt wrote:
I have been digging through the archives for a way to list queries that have output files.

Just about every one says to use RTVQMQRY.
I've tested a few that definitely have an outfile but they don't show up in the source after running that command.

Is there a parameter I'm missing or something? Couldn't find any.

RTVQMQRY QMQRY(&ODLBNM/&ODOBNM) +
SRCFILE(TRSFDD/QQMQRYSRC2) ALWQRYDFN(*ONLY)
Tried it with *Yes, also.

Some of the messages in the archives are VERY old, so it can't be our release level [V5R2].

Even looked at ANZQRY which wasn't what I was looking for although I did get the following information. Why is it saying it ignored the output options? It works.

Query definition TR_DAILY in TRLIBOBJ has dependent values
Field DLGLDT editing uses no decimal positions.
Different editing will be used for field DLGLDT.
Printer related choices ignored.
Database file output options ignored.
Analyze completed for query TR_DAILY in TRLIBOBJ, code 11.

Thanks,




Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Frances.Denoncourt@xxxxxxxxxxxxxxxxx
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.