Re: global MONMSG to catch everything

> BUT PLEASE BE CAREFULL!  What you are talking about doing is VERY
> dangerous!  And unfortunately, the shops that have the biggest
> problems with unhandled escape messages are then ones that SHOULD NOT
> USE THIS TECHNIQUE!  This is because if you can't trust your
> programmers (or vendor) to produce software that runs clean, how can
> you trust them to SAFELY implement something like a global MONMSG
> CPF0000????

Amen! It's been my experience that this technique usually ends up covering
up errors and making it very difficult to correct a problem that could be
corrected on the spot, rather than having to figure out first where the
error actually occurred, by which time it is no longer possible to get a
program dump which is usually invaluable in finding decimal data errors, and
second, figuring out what's required to rerun the job.

In most of the shops I've worked in, there is usally a mix of
vendor-written, and home-grown software, neither of which uses the others
standards. I've always found it a lot easier to find a problem if the job is
sitting on the error message where it first occurs.

> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---


__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---