|
Vern -To prevent STRSQL from wrapping printed output, BEFORE issuing the STRSQL command issue this command:
OVRPRTF FILE(QPQUPRFIL) PAGESIZE(*N 198) CPI(15) OVRSCOPE(*JOB)(I use OVRSCOPE(*JOB) because I'm not necessarily going to STRSQL at the same or lower invocation level...)
Then STRSQL, change the output destination to print instead of display, and execute your SQL statement.
Be sure to DLTOVR QPQUPRFIL after exiting STRSQL... Regards, Steve----- Original Message ----- From: <vhamberg@xxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Monday, July 25, 2005 12:03 PM Subject: Re: printing from SQL Select stmt
A couple nice things about QMQRY: (1) you can also create a QMFORM that gives you nice formatted output - similar to a Query/400 layout; (2) If the report (default or custom QMFORM) is wider than the page width, QM will create sets of pages that will cover the full width. When printing from STRSQL I got wrapped records, which are a bear to read, and in Query/400 the records are truncated, usually.To create the forms, use STRQM - licensed SQL product is required, but you have it if you have STRSQL.HTH Vern-------------- Original message --------------STRSQL F13=Services 1. Change session attributes SELECT output . . . . . . . . 1 1=Display, 2=Printer 3=File A simple SELECT statement is NOT allowed in RUNSQLSTM. Remove the semicolons from the RUNSQLSTM and then CRTQMQRY QMQRY(ROB/FRANZ) SRCFILE(ROB/QSQLSESS) STRQMQRY QMQRY(ROB/FRANZ) OUTPUT(*PRINT) Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Jim Franz" Sent by: midrange-l-bounces@xxxxxxxxxxxx 07/25/2005 10:55 AM Please respond to Midrange Systems Technical Discussion To cc Subject printing from SQL Select stmt Is there an option to print the results of a Select statement from within STRSQL or RUNSQLSTM? jim franz -- 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. --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo 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.--This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo 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.
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
