RE: Run SQL statement output

[Jerry Adams <jerry@xxxxxxxxxxxxxxx>]

One can use the Outq and ExpDate keywords in V5R4, too.  I can see that it might in some cases be a good idea to save the report.  The reason I don't use that method (once the kinks are ironed out, of course) is because the user sees it every time they run the WRKSPLF command; would just confuse the heck out of 'em.  Unless one went through the gyrations to change the current user profile running the procedure, which I'm too lazy to do, and used the SplfOwn keyword.

Just my personal preference, of course.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email:  jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of mkirkpatrick@xxxxxxxxxxxxxxxxx
Sent: Tuesday, June 23, 2009 9:57 AM
To: Midrange Systems Technical Discussion
Subject: Re: Run SQL statement output

I tend not to delete them but put them in QEZJOBLOG for 1 days, in case I 
need to review the log.

At IBM 6.1:
OVRPRTF    FILE(QSYSPRT) OUTQ(QEZJOBLOG) EXPDATE(*DAYS)  DAYS(7) before 
the RUNSQLSTM

At V5R4:
OVRPRTF    FILE(QSYSPRT) HOLD(*YES) before the RUNSQLSTM and then
DLTSPLF    SPLNBR(*LAST) 

I am sure there are other ways also.






From:
"Lance Gillespie" <lgillespie@xxxxxxxx>
To:
<midrange-l@xxxxxxxxxxxx>
Date:
06/23/2009 07:51 AM
Subject:
Run SQL statement output
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



When I run a CL that has a RunSQLStm in it, it produces a spool file
listing the source and run parameters and warnings even though
I specify OUTPUT(*NONE) for the Listing output parameter on 
the RunSQLStm command.

We are on v5r4.

How do I suppress this printed output?

Thanks,
Lance