RE: Use of DUMP in production programs, WAS: RPG enhancement suggesti on

I would like to continue to see unreferenced fields included in a dump. The
additional information that they provide has proved usefull to me in the
past. However, I have no problem with something like DEBUG(*NOUNREF), where
the programmer could override this behaviour.


John Taylor



> -----Original Message-----
> From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
> Behalf Of boldt@ca.ibm.com
> Sent: Wednesday, June 23, 1999 8:48 AM
> To: RPG400-L@midrange.com
> Subject: Re: Use of DUMP in production programs, WAS: RPG enhancement
> suggesti on
>
>
>
>
> Buck wrote:
> >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.
>
> How professional does your s/w look if the user has
> to call support for help?  (Sorry, couldn't resist!)
>
> I do see your point, though.
>
> A simple, one-liner for us would be to ignore the
> DEBUG keyword when deciding whether or not to
> extract an input field.  As a result, unreferenced
> fields would not appear on the dump, even with
> DEBUG(*YES) coded.  If a field is not used within
> a program, do you really care about its value?
>
> How about a quick vote on some alternatives:
>
> 1) Don't show unreferenced fields on dump.
> 2) Keyword DEBUG(*ALLOW) which would allow the
>    DUMP opcode to run, but unreferenced fields
>    wouldn't be extracted.
> 3) Opcode DUMP *FORCE to force a dump to occur
>    even if DEBUG(*YES) is not coded.  (Again,
>    unreferenced fields would not be extracted.)
>
> I'll add the results of the vote to our proposed
> enhancements list.
>
> 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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *