As Rob said, do an ovrprtf to to handle the width of your report. What you are getting is the "feature" of QM forms that I like - reports wider than the PRTF width end up with multiple spooled files that you'd have to tape together to see them all. The output from interactive SQL and from Query/400|iSeries|i always truncate the output.

I think the prtf name is QPQXPRTF - its default width is 80 characters. Note that QPQUPRFIL, the prtf for interactive SQL and Query, has a default width of 132. I just noticed that the replacement character for unprintable is different from one to the other of these prtfs - interesting.

You might consider using less space between columns - default is 2 in STRQM. You might also consider making longer text columns narrower - e.g., for a 100-char, use a column width of 30 - and then use the CT edit code (I think that's it) - that will wrap the text within the column width honoring word breaks - very cool.

Put the override in your CL just before you do the STRQMQRY - if in STRQM, do it before you get in there, or else use F21 to get a command line and set it.

Gotta love QM forms and queries!!

HTH
Vern

Emily Smith wrote:
I'm attempting to create a report in query management that will hopefully look something like this.....
ATM Watch Notification Log Terminal Incident Date Time Method Contact Message -------- ---------------- -------- -------- ------ ----------
------------------------------------------------------------ 1234 I000000000004137 09/01/09 10:27:39 Joe Smith Communication Lost 1234 I000000000004137 09/01/09 10:27:53 Joe Smith Down too Long 1234 I000000000004137 09/01/09 10:28:08 Bill Jones
Communication Restored
With the Page heading and column headers repeating at the top of each page.
Unfortunately, that's not the result I'm getting. When the query is run I end up with only the page heading on page one. Page two then prints as I expect with the page heading centered at the top then column headings, and then data. Page three prints with no page heading or column headings just the detail. Then Page 4 prints like page one with only the page heading and nothing else. This pattern repeats to the end of the report.
Here is the screen shot of the page heading in work with query manager report forms
Edit Page Heading Type choices, press Enter. Blank lines before . . . . . . . . . . . . 0 0-999 Blank lines after . . . . . . . . . . . . 1 0-999 Page text: Use &col, &DATE, &TIME, and &PAGE to cause variable insertion. Line Align Page Heading Text 1 CENTER ATM Watch Notification Log This is the strqmqry command from my joblog
STRQMQRY QMQRY(EMILY/AWNTFYRPTQ) OUTPUT(*PRINT) QMFORM(RUNCUS/AWNTFYRPTT) DATETIME(*NO) PAGNBR(*NO) NAMING(*SQL) SETVAR((BEGIN '''2009-09-01''') (END '''2009-09-01''') (DEVICENO '1234')
Any help or insight would be greatly appreciated. TIA
Emily Smith
Programmer/Analyst
Bank Data Services
(618)659-4550
CONFIDENTIALITY NOTICE: This email message is private, confidential property of the sender, and the materials may be privileged communications intended solely for the receipt, use, benefit, and information of the intended recipient indicated above. If you are not the intended recipient, you are hereby notified that any review, disclosure, distribution, copying, or taking of any other action in reference to the contents of this message is strictly prohibited, and may result in legal liability on your part. If you have received this message in error, please notify the sender immediately and delete this message from your system. We believe that this email and any attachments are free of any virus or other defect that might affect any computer system that it is received and opened in, however, it is the responsibility of the recipient to ensure that it is virus free and the sender accepts no responsibility for any loss or damage.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].