RE: RPG enhancement suggestion

Yes, this is true, but in my case, we develop software for other
companies, 
and do not want users seeing system error messages that they can either
chose to enter a 'D' to dump or a 'C' to cancel if theres an error. 

We want a DUMP to always occur if theres an error.
Our standard is to have error processing at every point in the program
where an error could occur, particularly files. 
We place markers in the source so that we can trace a problem by looking
at the values of the markers in the DUMP. 

Many of our clients are in other countries, ie other time zones
so may not be able to call us until a few hours after the error has
occurred. So basically we always want a DUMP if an error occurs, we dont
want it to be optionally. 

We could rerun and reproduce to the error, but you can't ask a bank or a
factory to rerun their entire end of day. 
In some cases this is just not possible.

So we always need a DUMP to be produced automagically, without user
intervention.

-----Original Message-----
From: boldt@ca.ibm.com [mailto:boldt@ca.ibm.com]
Sent: Wednesday, June 23, 1999 1:01 PM
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

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
* 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
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *