MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2008

RE: Query Management Reports Problem



fixed

Well, Vern, after posting my question I thought about the OVRPRTF command. It works, of course. Just thought that, since little, old Query/400 was smart enough to format printing for wide reports, that its big brother ought to be able to do so, too. When working on a new query, it's nice to be able to print the report. I just have to remember to issue the OVRPRTF command before I STRQM.

A possible solution, at least for me, is to put the Override in my startup procedure. At least, then, I wouldn't have to think about it; an advantage to people of our advanced years!

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of vhamberg@xxxxxxxxxxx
Sent: Wednesday, June 04, 2008 5:17 AM
To: Midrange Systems Technical Discussion
Subject: Re: Query Management Reports Problem

The OVRPRTF is probably the easiest way to accomplish the goal. However, Query Management has a lot more to it, and there are other ways - not to say I've used them. E.g., there is a QM command, PRINT, that includes a WIDTH parameter. This can be executed using a Callable Interface - CI. The same CI can also be used to set the values of replacement variables. All this information is in a manual called "Query Management Programming". It's located at InfoCenter under Database in all the recent releases. That's where the information is related to the printer files used by QM. Also some of the same suggestions we have posted here.

There are also things called QM procedures, although I've not looked at those in a while and do not remember if you can pass values to them - they are source members, after all.

So Jerry, you old dog, there are some more tricks to learn!!

Vern

-------------- Original message --------------
From: "Aaron Abreu" <abreual@xxxxxxxxxxxxx>

Jerry,
you are correct, the ovrprt runs first everytime,
but its not extra work, the CL is compiled and
run from a CALL command so actually, once
written, I never even see this part again,

and---a big advantage to me for my work..
I can modify the source sql as many times as I
want too, and never have to touch the CL again.
unless the sql fields add up to a report so wide
that the size parameters in the CL no longer
keep it on 1 page.. thats pretty rare.. maybe
1 time year..

HTH
Aaron
--
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact