Re: Query management forms -- MIDRANGE-L

Dean

I have a PMR in to partner support at IBM - will see if they can tell a way to do this. The support guy did not hold out much hope of a change, because IBM are pushing Web Query.

I did a quick test of a minimal QMFORM source - no luck - the Query Management manual you mention might say which records are required - seems almost all are!

Will come back with more info if and when I get it.

BTW, I think QM is a great technology to know about - I use it all the time and recommend it to customers who want to create reports quickly - I think it can be much more flexible than RPG, and faster to create. Web Query is intended, as far as I can see, for clients, not for production jobs. I've helped a few customers learn it, and they love it.

Vern

Dean.Eshleman@xxxxxxxxxxxxxx wrote:

Vern,

I was trying to figure out if I could create a predefined generic form with a header as a variable and nothing else specified, but I don't think that will work. Probably the only thing that would work is creating the form on the fly. That is probably more work than I want to do. Like you say, the source for QM forms is not for the faint of heart. I looked at a manual that talked about the record types and codes to use, but it sure seemed complex. That is why I posted my original message to see if anyone could help me out. : ) I think I may be out of luck though since I'm sure not many people use QM forms anymore. A clunky approach may be my only option.

Dean Eshleman,
MMA, Inc.

On Mon, 25 Jan 2010 17:50:04 -0600, in midrange.midrange-l you wrote:

He wants a dynamic header based on a generic SELECT statement - there is no form source file for the *SYSDFT form, is there? He wants to have some header text to put in the *SYSDFT form.

OK - so are you saying to create the source for the form? QMFORM source is not for the faint of heart, although I've not tried one with just the header line in it. Maybe can be done that way.

Hmm - you have to use RTVQMFORM to get the form source. Since there's no form to retrieve from - ???

Vern

Alan Campin wrote:

The input to the form is just a text file that you can retrieve
(RTVQMQRY)

so there is nothing to keep you from writing the text member and just
putting your own headers into the text. The time to create the form is
sub-second. Create the report, retrieve the text and write out with
your own

headers and do a CRTQMQRY.

On Mon, Jan 25, 2010 at 2:02 PM, Vern Hamberg <vhamberg@xxxxxxxxxxx>
wrote:

True enough - better than nothing but not much! Not much choice when
he

wants a dynamic page heading - unless some IBMer here has a secret
technique for specifying that heading - maybe in a message description
or something!!

Vern

sjl wrote:

Vern -
Correct, but the overridden Print Text will print at the /bottom/ of
the

QM

Query report...
- sjl

"Vern Hamberg" <vhamberg@xxxxxxxxxxx> wrote in message
news:mailman.4297.1264207340.2580.midrange-l@xxxxxxxxxxxxxxx
Yes, but Dean wants a dynamic layout, the same as the default but
with

his own report heading.

I don't think this can be done - too bad.

You might try saying *YES to date/time and page numbers, which go on
the

bottom of the page. And for some report description, use the print
text

parameter of OVRPRTF QPQXPRTF

HTH
Vern

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

______________________________________________________________________
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmissions errors in the future. Thank you.