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


  1.  Home
  2. RPG400-L
  3. February 2010

Re: Uncaught Errors in Interactive Programs and the Users that Ignore the Errors

Rob

I really don't see how this is contrary to what I said about having a general error handler in the event of completely unexpected errors - that, as far as I'm concerned, is what that top-level MONMSG is for - period.

So unless you really are looking for controversy, I see none.

:-)

rob@xxxxxxxxx wrote:
Ok, so you get the pretty error handling email "shirts wrong - go fix it" with that kind of go to.
But if your job stream was 27 pages of cl and you're on page 20 and don't have good restart procedures it can be dicey. That's why I prefer the ability to use R to retry.

Then again, should you be running the job from hell interactively instead of batch? Or, if you just have to have a pretty status bar, have the batch job put entries on a data queue and your interactive job can process that.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.