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



You mean System I programmers should mimic IBM and make error handling an integral part of the development process? What an idea!

Gary Monnier


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Friday, January 13, 2012 12:27 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Pet peeve about users

On 1/13/2012 3:06 PM, Jon Paris wrote:

Why is it that programmers don't write their programs so that users
only ever see meaningful messages and not the green screen of death?


And while the program is preparing the meaningful message, it can also be sending the joblog and dspjob (open files, locks, call stack, etc) in an email, or storing them somewhere so the end user doesn't even have to know about it.

The dspjob and dspjoblog should probably be captured at the exact time the error happens, either by using the message watch facility, or a CEEHDLR handler (that just looks at error messages without trying to handle them).
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.