MONMSG on RUNSQL in CLLE program -- 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: MONMSG on RUNSQL in CLLE program
From: Dan <dan27649@xxxxxxxxx>
Date: Fri, 5 May 2017 18:59:35 -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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

From https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/cl/runsql.htm,

it appears that the only messages that can be monitored on RUNSQL are
SQLxxxx, SQ2xxxx, and SQ3xxxx messages.

Does anyone know whether monitoring for SQL0000, SQ20000, and SQ30000 will
trap all of the SQLxxxx, SQ2xxxx, and SQ3xxxx errors? Will SQ*nnnn
messages that are really *not* errors be flagged as well?

- Dan

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: MONMSG on RUNSQL in CLLE program , Hiebert, Chris
RE: MONMSG on RUNSQL in CLLE program , Jim Oberholtzer

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.