|
I do a lot of one-timer SQLs, some for testing before embedding in anapplication, 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
(F13=Services, 1.Change session attributes, SELECT output: 3=File).
The one that I have running now is set up to send output to a data file
specified in the SELECT, then submit to batch a RUNSQLSTM with the same
I suppose the way to do this is to create the output table with the fields
query, but prefaced with a "INSERT INTO xxxxxxxxxx (" It seems to me thatthis would give the same results. Any disagreement there?
I have to put the query in a source member for the RUNSQLSTM, and then
But what a PITA! First, I have to manually create the output table, 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!
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.