RUNSQLSTM -- MIDRANGE-L

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

Subject: RUNSQLSTM
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Date: Mon, 31 Mar 2008 15:49:18 +0200
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: RUNSQLSTM , darren
RE: RUNSQLSTM , Elvis Budimlic

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.