Re: Send email on program halt -- 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: Re: Send email on program halt
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Date: Wed, 2 Sep 2015 17:02:34 -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>

On Wed, Sep 2, 2015 at 4:31 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

And FYI MPLUS is actually even smart enough to differentiate between a
MSWG caused by an escape message and MSGW in a never ending job that's
using the receive message API to wait for a message to process.

Ok I take that back...

The monitors I posted aren't that smart.

But you can exclude jobs from being caught by them.

Also there's another monitor for QSYSOPR
RPG, COBOL, CL batch error messages

That catches exceptions thrown by batch jobs.

Charles

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.