RATE THIS ANSWER
0
Click to Vote:
- 0
0
Last Answered:
Mar 6 2008 10:31 PM GMT
by Bvining
I don't know that you can prevent it, but you sure can hide it or kill it :-)
One "hide it" option would be to:
CRTOUTQ TEMP
CRTPRTF TEMP OUTQ(TEMP)
RUNSQLSTM ... PRTFILE(TEMP)
and then periodically CLROUTQ TEMP
A "kill it" option would be to, in your CL program, simply DLTSPLF xxx SPLNBR(*LAST) where xxx is the name of your source member right after the RUNSQLSTM command runs successfully.
Bruce Vining
http://www.brucevining.com/ Integrated solutions for the System i user community
RUNSQLSTM, CL, SQL
am executing a RUNSQLSTM out of a CL program that run a source SQL statement in a source file of a library. Everytime the statement is executed I get a output spool file of the SQL parmeters and execution results. How can I prevent this? 
