There's really no way to suppress the output, but there are ways to more
easily handle the clutter.
One way I used to use in the past is something like this:
OVRPRTF QSYSPRT OUTQ(QUSRSYS/GARBAGE)
RUNSQLSTM SRCFILE(mylib/SQLSRC) SRCMBR(mymbr) COMMIT(*NONE)
DLTOVR QSYSPRT
and then ADDJOBSCDE to CLROUTQ QUSRSYS/GARBAGE once a day or something.
But then I saw a post that looks like a better solution:
CHGCMDDFT CMD(RUNSQLSTM) NEWDFT('PRTFILE(*LIBL/TRASH)')
And then clear TRASH on daily basis or something.
Elvis
Celebrating 10-Years of SQL Performance Excellence
http://centerfieldtechnology.com/training.asp
-----Original Message-----
Subject: RunSqlStm output
Anyone know if the output listing from executing RunSqlStm can be
suppressed?
Buzz Fenner
Systems Analyst/Network Administrator
870.930.3374
mailto:bfenner@xxxxxxxxxxxxxxxx <mailto:bfenner@xxxxxxxxxxxxxxxx>
This mailing list archive is Copyright 1997-2026 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
