RE: RUNSQLSTM

["McCune, Dave" <Dave.McCune@xxxxxxxx>]

What I use is a DLTSPLF, with the *LAST and then monitor it just to make
sure the job doesn't stop.
DLTSPLF    FILE(xxxxxxxxxx) SPLNBR(*LAST) 
MONMSG     MSGID(CPF0000)               


David McCune
SR. Programmer Analyst
Fike Corp
Blue Springs, MO
816-655-4577

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] 
Sent: Thursday, June 16, 2005 9:02 AM
To: midrange-l@xxxxxxxxxxxx
Subject: 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.  

--
Jeff Crosby
Dilgard Frozen Foods, Inc.
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.