|
Hi Antonio - >I have been digging for some time looking for automating retreiving info >on queries built with Query/400, i.e. those based on specifications of >type *QRYDEF. >I found everything about API QQQQRY, and it seems reading thru the >queries template would do the work I need... Everything seems hendy... >except for the main question: You are misunderstanding the function of QQQQRY. It has nothing to do with retrieving information about existing queries, whether Query/400 or QMQRY. It is an interface to the query engine. That is, you build your own query definition template and pass it to QQQQRY and you will get back the result set that meets the specifications of your query template. >How can I retreive the QDT (Query Definition Template) of any given >Query???? (one that already exists). You can't do it with QQQQRY. If you want just a limited subset of information you can use RTVQMQRY with ALWQRYDFN(*ONLY). If you want to know everything about a query, you will probably have to retrieve the query object through MI or through DMPOBJ and copying the spooled file to a data base file, then write your own program to parse the data into something meaningful. Ken Southern Wine and Spirits of Nevada, Inc. Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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-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.