|
You're encountering the dread query management form and probably the default print file. It gets complicated from here out. You can do almost any of the things you can with Query400, but you may need to use query management forms, which can be extracted from your Query400 query with RTVQMFORM, and you may need to override the print file to get widths over 80 columns. You can also try prompting the STRQMQRY and exposing all parameters. For the QMFORM parm specify *QRYDFN and don't forget to specify ALWQRYDFN *YES. I recommend, but with the usual caveat that it is an IBM manual, "OS/400 DB2 for OS/400 Query Management Programming." There are some differences on summary functions explained in one of the appendices. If there's anyone out there who actually constructs qmforms from scratch, I'd be real interested in picking up some tricks of the trade. The manual is a model of obscurity on the syntax of the qmform. O specs are transparent by comparison. Good luck. > -----Original Message----- > From: Ladutko, Bob [mailto:Bob.Ladutko@bicworld.com] > Sent: Wednesday, December 30, 1998 10:02 AM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: Passing parms to query > > > > At the risk of looking dumb (again), when I run STRQMQRY > against a query > definition, I don't get any of the query's formatting. > (Column headings, > summary functions, report breaks, etc. are ignored). Am I > doing something > wrong (which I've been known to do on occasion), or is the > query definition > always ignored by STRQMQRY? > +--- | 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-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.