MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

RE: Scaning field JSLIBL from QAUDJRN outfile QASYJSJ5



fixed

Chuck,

Changing the * to JSJOB reduced the number of spoolfiles to 1.

Thanks
Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, July 16, 2014 9:56 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Scaning field JSLIBL from QAUDJRN outfile QASYJSJ5

On 16-Jul-2014 20:02 -0500, Steinmetz, Paul wrote:

<<SNIP>>

I changed the SQL slightly, to run in batch, via AJS.

Cause . . . . . : Command to execute is:
RUNSQL REQUEST('select * from qgpl/QASYJSJ5
where locate (''ARPINS2'',JSLIBL ) <> 0') OUTPUT(*PRINT).

But now I got 33 1 line spoolfiles (see below), not the expected
result.

Any suggestions for batch.

<<SNIP QMQRY report>>


The QMQRY spool output to QPQXPRTF is implemented as side-by-side, and a full report is generated even for zero records. Change the asterisk as column-list to some columns of interest, for which the default form [default *QMFORM] will not produce multiple SPLF, and the effect of a no-records result-set report will be more conspicuous.

There is no /easy/ way to cause the QM Query to fail for zero rows, although I recall discussing possible attempts at effecting a failure in such cases; on an\the Italian AS400 USENET group.

--
Regards, Chuck
--
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact