RE: RUNSQLSTM

["DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>]

Perhaps you could just override the printer file to point to a file in QTEMP....

Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of David FOXWELL
Sent: Monday, March 31, 2008 10:18 AM
To: Midrange Systems Technical Discussion
Subject: RE: RUNSQLSTM


Er.. sorry  I meant I didn't want to generate the unnecessary spoolfile in the first place.

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de darren@xxxxxxxxx
Envoyé : lundi 31 mars 2008 15:59
À : Midrange Systems Technical Discussion
Objet : Re: RUNSQLSTM

Something like this doesn't get rid of it?
DLTSPLF FILE(QSYSPRT) SPLNBR(*LAST)




             David FOXWELL
             <David.FOXWELL@ag
             ipi.com>                                                   To
             Sent by:                  Midrange Systems Technical
             midrange-l-bounce         Discussion
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>
                                                                        cc

             03/31/2008 09:49                                      Subject
             AM                        RUNSQLSTM


             Please respond to
             Midrange Systems
                 Technical
                Discussion
             <midrange-l@midra
                 nge.com>






Hi,

I've just put a RUNSQLSTM in a program. Its the first time I've used this command for a program intended for production. I've been told to get rid of the spoolfile generated by this command, but I can't see how to do it. In the CL program I use MONMSG SQL0000 directly after the RUNSQLSTM. It would be good if I could keep the spooled output if any errors were generated.

Any ideas ? Thanks.
--
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.



--
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.