×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.