RUNSQLSTM Monitor -- 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 Monitor
From: michaelr_41@xxxxxxxxxxxxxx
Date: Mon, 28 Jun 2004 11:20:58 -0400
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>

How does one monitor for errors when using RUNSQLSTM? I have member
containing a couple of DROP INDEX statements. The process blows up if
the specified index isn't found. I know I can do a DLTF in CL and
monitor for the appropriate message, but I'd like to be able to do this
in SQL.

TIA...
-- 
  
  michaelr_41@xxxxxxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: RUNSQLSTM Monitor , 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.