Re: Use of DUMP in production programs, WAS: RPG enhancementsuggesti on

[Dave Shaw <dshaw1@xxxxxxxxxxx>]

Hans very cooperatively wrote:

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

Either 2 or 3 would be great.  There have been times when I've wanted the
unreferenced fields for record identification, so I'd still like to have a
way to get them.  I don't like option 1 for that reason.  Thanks!

---
Dave Shaw, General Nutrition, Greenville, SC
To subscribe to the MAPICS-l mailing list send email to
MAPICS-L-SUB@midrange.com
The opinions expressed may not be my employer's unless I'm sufficiently
persuasive...



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