Re: Catching errors on user screens

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Oliver,

You wrote:
>well, as one of our apps we have an old BPCS implementation.

A fine example of how not to write code.

>Any trick to stop these users cold at the error screen? I preach to them 
>every other day to at least press 'D' and Enter, so I get a dump.
>But most of the time they'll just do enter.

Users should NEVER EVER see this error screen because they are not qualified to 
answer the message. Each program should have generic error handling that 
catches 
the error, collects diagnostic information, notifies support, and tells the 
user 
that someone from IT will be contacting them about the problem. You could also 
disable the menu option to stop them from running it again until the problem 
has 
been investigated.

One way to do that is to code a *PSSR subroutine in the program and have it do 
all the above steps and then exit cleanly. You should also specify the *PSSR as 
the INFSR for each file processed by the program.

Write it once in a /copy member and include it in every program you have.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists       
                                                                  
   http://www.flybynight.com.au/                                  
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\   
   Fax:   +61 3 9419 0175   mailto: shc@xxxxxxxxxxxxxxxxx   \ /   
                                                             X    
                 ASCII Ribbon campaign against HTML E-Mail  / \   
--------------------------------------------------------------------