You can define headings but you have to use the form functionality to do
it and it is not well documented. If you do a shift f1 (F13) in the SQL
window, it allows you to create a form attached to the qmqry that
contains headers, footers, break text, etc.
Check out chapter 6 in DB2 Universal Database for iSeries
Query Management Programming
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Tuesday, July 29, 2008 1:43 PM
To: Midrange Systems Technical Discussion
Subject: Re: Way to get STRSQL SELECT to run in batch?
I think QM is one of the best least known things around. And a form can
be used to go to a display, as well as a spooled file - you just don't
get page headings and all that - you still get the outlined rows, where
repeated values can be suppressed - all that.
Of course, the form means nothing if output is an *OUTFILE.
-------------- Original message --------------
From: "Carel Teijgeler" <coteijgeler@xxxxxxxxx>
Use query Manager (QMQRY). You can save you query in an QMQRY object,
wanted create a report model (QMQRY FORM) as well (only for printing).
Related commands are STRQM, which allow you to maintain QM queries.
STRQMQRY lets you run an existing QMQRY.
Output can be directed to screen, printer or PF. The PF does not have
exist, it will create it. Existing PFs can be created with DDS.
Good luck with it.
*********** REPLY SEPARATOR ***********
On 29-7-2008 at 12:13 Dan wrote:
I do a lot of one-timer SQLs, some for testing before embedding in an
application, some for data interrogation to determine problems.
doesn't support SELECT, otherwise I'd use that to submit to batch.
Some of the SELECT queries I do, run for hours. Of course, RUNSQLSTM
The one that I have running now is set up to send output to a data
(F13=Services, 1.Change session attributes, SELECT output: 3=File).
I suppose the way to do this is to create the output table with the
specified in the SELECT, then submit to batch a RUNSQLSTM with the
query, but prefaced with a "INSERT INTO xxxxxxxxxx (" It seems to me
this would give the same results. Any disagreement there?
But what a PITA! First, I have to manually create the output table,
I have to put the query in a source member for the RUNSQLSTM, and then
the RUNSQLSTM. There's gotta be an easier way.
FWIW, here's the query that's now in its third hour:
select DISTINCT CVCVCD, CVCVLC, CVDEDC, count(*)
from cvgdetl, cusdetl_DE
where CVCUSN = cdCUSN
and CVRENN = cdRENN
and CVSEQN = cdSEQN
and cdstat = 'DE'
group by CVCVCD, CVCVLC, CVDEDC
Any ideas would be greatly appreciated!
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives