Re: RUNSQLSTM

> Is there a way to keep RUNSQLSTM from generating printed 
> output?  I'm running it with OUTPUT(*NONE) but it still 
> generates a spool file.

I asked the above the other day.  After scouring InfoCenter and googling
till I was looking for a rope, I finally found the following tip from Ted
Holt:

<tedshelp>

Avoiding Output from RUNSQLSTM

Hey, Ted: 

I have recently started using Run SQL Statement (RUNSQLSTM) and have saved
myself a lot of time. Instead of taking hours to develop an RPG program, I
can whip up a functionally equivalent SQL statement in a few minutes.
However, I have one slight problem. RUNSQLSTM produces a status report that
prints out on the users' printers. They are annoyed, and it's a waste of
paper. How can I keep these reports from printing? 

You would probably benefit from creating an output queue, say
QUSRSYS/GARBAGE, to which you could direct unwanted output. You can add a
job schedule entry (ADDJOBSCDE) to clear the queue automatically each day. 

To direct the output of RUNSQLSTM to the new garbage queue, issue the
Override with Printer File (OVRPRTF) command for file QSYSPRT, as the
following CL code illustrates: 

OVRPRTF QSYSPRT OUTQ(QUSRSYS/GARBAGE)
RUNSQLSTM SRCFILE(mylib/SQLSRC) SRCMBR(mymbr) COMMIT(*NONE)
DLTOVR QSYSPRT

</tedshelp>

The above leads me to believe there is no way to stop the spool file from
being generated, so I took his advice.