|
Hi Peter
I don't have all your answers, maybe a couple.
Query for i is Query/400 - at least you don't have an AS/400, right?
QM and Query for i do have their differences, of course. I'd forgot, I think, of the layout you describe. As I recall, there's nothing like that QM can do. Now was that on several pages, or was it only on a cover page?
OTOH, I have liked how QM will print to multiple kind-of parallel SPLFs if the output record is wider than the PRTF width. Query tended to truncate - or is the a fold setting in the print settings?
It would be interesting and maybe instructive to use ANZQMRY on the Query for i QRYDFN that has this layout and see what you get in the job log - there will probably be messages about the things QM can't do.
Interesting stuff!
Vern
On 7/24/2020 4:00 PM, Peter Dow wrote:
When I started to write this email, I realized I'm not sure of the current naming for IBM i's query products.
Near as I can tell Query/400 refers to WRKQRY, RUNQRY, etc., QM Query refers to STRQM, STRQMQRY, etc. and I have no experience with Db2 Web query.
On a 7.3 IBM i, under installed licensed software, I see 5770QU1 IBM Query for i. I don't know what this includes.
My real question involves a difference in how Query/400 queries and QM queries format their reports.
In Query/400, it is possible for one selected record to print on multiple lines on the same page. For example, if a record contains a name, address lines, city, state, zip and phone#, it is possible for the query to print
Name
Address Line1
Address Line2
City, State Zip
800-555-1212
all on the same page in a single spool file.
Trying to do the same in QM query results in multiple spool files. Reading the Query Management Programming manual (SC41-5703), when working on column formatting, the edit codes for a character column include CW says
"Makes no change in the display of a value, but if the value cannot fit on one line in the column, query management wraps the text according to the width of the column. That is, instead of truncating the data at the end of the column, query management puts as much data as possible on one line in the column and then continues the data on the next line in the column."
Not exactly the same thing, but close. To do the same thing as Query/400, I would have to concatenate all the fields into one, then use the CW edit code. That means I lose a lot of ability to format individual fields.
What I would like is a way within QM Query to wrap a record at the page width, but keep the additional lines within the same spool file.
Has anyone else run into this and found a solution?
--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /
--
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
