Use of DUMP in production programs, WAS: RPG enhancement suggestion

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

Hans,

Generally speaking, I'd rather that the end-user not see "white messages."
I would much rather trap the error myself, produce a post-mortem dump and
tell the user to call support for help.  My software looks much more
professional telling the user to call support than if an "Invalid array
index" error pops up.

Buck Calabro

> -----Original Message-----
> From: boldt@ca.ibm.com 
> Sent: Wednesday, June 23, 1999 8:01 AM
> To:   RPG400-L@midrange.com
> Subject:      RE: RPG enhancement suggestion
> 
> 
> 
> Colin wrote:
> >This is what happens if you specify DEBUG(*YES) in your programs,
> >which is included so that a DUMP can be produced as part of the error
> >processing,
> >but also means that every field is read in from every file.
> >
> >This is the standard at my current company,
> >and at every other place that I have worked, where they include the DUMP
> >opcode as part of their error processing.
> 
> DEBUG(*YES) is necessary to be able to use opcode DUMP,
> but a dump is always possible without DEBUG(*YES).  The
> "D" reply to any RPG exception will give you a dump even
> if DEBUG(*YES) is not coded.
> 
> I would assume that printing a DUMP is only really needed
> when you get some unexpected exception, and so you'll have
> the opportunity to ask for the dump anyways, right?
> 
> Cheers!  Hans
> 
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *