Re: SQL output to Printer - anyway of marking/tagging the spoolfile with the PF name -- MIDRANGE-L

Subject: Re: SQL output to Printer - anyway of marking/tagging the spoolfile with the PF name
From: CRPence <crpbottle@xxxxxxxxx>
Date: Tue, 27 Sep 2016 12:10:42 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 27-Sep-2016 11:31 -0500, Rob Berendt wrote:

Then there's always

SELECT "LIB1", "FILE1", Date-field,count(*)
FROM LIB1/FILE1
GROUP BY Date-field
ORDER by Date-field
UNION ALL
SELECT "LIB2", "FILE2", Date-field,count(*)
FROM LIB2/FILE2
GROUP BY Date-field
ORDER by Date-field
UNION ALL
SELECT "LIB3", "FILE3", Date-field,count(*)
FROM LIB3/FILE3
GROUP BY Date-field
ORDER by Date-field

and get it all in one spool file.

That statement is not syntactically correct, not even for COBOL ;-)

But more problematic is the [possible lack of, or quite likely undesirable] collation [per either lack of, or illogical, ORDER BY], depending on how the statement is redacted to get past the issue with the syntax.

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.