On Wed, 2 Sep 2015, Buck Calabro wrote:

On 9/2/2015 3:36 PM, Charles Wilt wrote:
Can't be done.

Either the job stops, or the job doesn't stop (and sends an email).

You'd need an external process that monitors for the MSGW and sends an

A possible alternative is to MONMSG (ie trap the error), in the DO()
send the email and then re-throw the exception.

I thought about this but couldn't come up with a satisfactory way to do it. Many programs are called during the execution of the daily close and I'd want execution to stop at the original point of execution of the error.

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.