|
Hi Michael
Yes, you can change the form, but QM does not have a setting for line
wrapping, as QRYDFN does, nor the FORMSIZE as RUNQRY does - now the width
of QPQXPRTF on one of our systems is 165. If your report, whether in a form
you create or the default form, if that report is wider than 165 in our
case, all the columns that will fit in the PRTF width will be on one SPLF,
If there are more columns, they go on another SPLF, until all columns are
printed.
To avoid the multiple SPLFs, you have either to CHGPRTF QPQXPRTF or
OVRPRTF QPQXPRTF to handle the width.
Your suggestion to create a form - yes, I agree. And one can use RTVQMFORM
from the QRYDFN to get a start on it.
You say it's not an OVRPRTF issue - yet you suggest using CHGPRTF -
personally I'd never do the latter, when an OVRPRTF does the job with no
change to system objects. Just me, right?
The Query Management programming manual has things in the appendix about
limitations of the conversions. Well worth a read, to minimize surprises.
Also, it used to be that if your QRYDFN had type 2 or 3 joins, the
conversion created only type 1 joins - that is different now since
somewhere around 6.1 - I have the info in presentation and lab I've done at
COMMON, but memory is leaking here, too.
Regards
Vern
----- Original Message -----
From: "Midrange Systems Technical Discussion" <
midrange-l@xxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxxxxxxxx
Cc: "Michael Mayer" <MMayer@xxxxxxxxxxxxxx>
Sent: Wednesday, April 20, 2022 10:45:51 AM
Subject: RE: Strange issue using QMQRY.
Boy, does this bring back memories. Also haven't used QMQRY in a very long
time.
I also converted all of my original WRKQRY's to QMQRY's back in the day.
I had a program that ran a DSPOBJD to an out-file and then ran a RTVQMQRY
over the out-file to a source file.
I'd take the source members and turn them into QMQRY's.
I recall the printed output would sometimes create 2 spooled files for
each QMQRY.
It's not an OVRPRTF file issue. It is a QMFORMS issue.
When using STRQM, once the QMQRY is written, a corresponding QMFORM should
Be created and the column width's adjusted to accommodate the output so 1
spooled file
Is created for each QMQRY. You can also change the report width from 132
to 198 as I also recall.
CAVEAT: IT'S BEEN A VERY LONG TIME SINCE I'VE DONE THIS SO IF I'M WRONG ON
THIS,
PLEASE CORRECT ME PEOPLE.
Very Respectfully,
Michael Mayer
IBM i on Power System Admin.
IT Operations.
The Florida Bar
651 E. Jefferson St
Tallahassee, Florida 32399-2300
mmayer@xxxxxxxxxxxxxx
https://www.floridabar.org
Office: 850.561.5761
Cell: 518.641.8906
IBM i Reference blog page: http://ibmireference.blogspot.com/
4. Strange issue using QMQRY. (a4g atl)
5. RE: Strange issue using QMQRY. (Rob Berendt)
----------------------------------------------------------------------
message: 4
date: Wed, 20 Apr 2022 11:23:54 -0400
from: a4g atl <a4ginatl2@xxxxxxxxx>
subject: Strange issue using QMQRY.
I have been changing/converting QRY/400 or *QRYDFN to Query Manager
Queries. The process is simple.
The strange problem I am experiencing now is STRQMQRY is producing 2 spool
files for each time a query is run.
The printer file is QPQXPRTF.
Does anyone know why this is happening?
TIA, Darryl Freinkel.
------------------------------
message: 5
date: Wed, 20 Apr 2022 15:29:24 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: RE: Strange issue using QMQRY.
Been a long time since I've done that.
Is this one of those OVRPRTF to more columns thing?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of a4g
atl
Sent: Wednesday, April 20, 2022 11:24 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Strange issue using QMQRY.
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
I have been changing/converting QRY/400 or *QRYDFN to Query Manager
Queries. The process is simple.
The strange problem I am experiencing now is STRQMQRY is producing 2 spool
files for each time a query is run.
The printer file is QPQXPRTF.
Does anyone know why this is happening?
TIA, Darryl Freinkel.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
------------------------------
Subject: Digest Footer
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
------------------------------
End of MIDRANGE-L Digest, Vol 21, Issue 464
*******************************************
________________________________
Please note: Florida has very broad public records laws. Many written
communications to or from The Florida Bar regarding Bar business may be
considered public records, which must be made available to anyone upon
request. Your e-mail communications may therefore be subject to public
disclosure.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.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.
midrange.com
