Re: RTVQMQRY does not retrieve outfile information

Vern,
Thanks. While I was waiting, I found reference to a program that is now here: http://archive.midrange.com/repository/extqrydef.htm

I think it might be what I want and hopefully, I can get it working.

There is a note in the memo to users about output files being formatted a little differently from IBM supplied commands when we go from V5R2 to V5R4. Wanted to avoid disasters, if possible.

Thanks again,


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

Vern Hamberg <vhamberg@xxxxxxxxxxx> 10/29/2008 3:12 PM >>>

Frances

QMQRYs know nothing about output options in QRYDFNs. So you will never
get any information about that with RTVQMQRY.

I believe there have been some utilities for figuring out what is in a
QRYDFN - maybe TAA Tools has one - it might be possible to read a DMPOBJ
output and find the place where output options are stored there - I
certainly don't have that internal object information, however - maybe
someone on this of the MI list.

Hmm - did a google on "qrydfn output" and came up with this link

http://archive.midrange.com/mi400/200406/msg00000.html

Follow the thread and you might be pleased.

Regards
Vern

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