RE: Use of DUMP in production programs

[Chris Bipes <ChrisB@xxxxxxxxxxxxxxx>]

Yes, I am in favor of changing the DUMP and what you see.
1. DEBUG(*ALL) - all fields are included - like today. - Default -
2. DEBUG(*REF) - Only referenced fields
3. DUMP *FORCE  *all/*ref - for those who don't want to code DEBUG.  Why
both, for programming styles.

I would also like to see the dumps formatted a little differently.
a. Include in header the line number that the DUMP opt code was executed.
b. Only show reference indicators when DEBUG(*REF).
c. Show source code line numbers when available instead of compiled line
numbers.



Christopher K. Bipes            mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst          mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                http://www.cross-check.com
6119 State Farm Drive           Phone: 707 586-0551 x 1102
Rohnert Park  CA  94928         Fax: 707 586-1884



-----Original Message-----
From: boldt@ca.ibm.com [mailto:boldt@ca.ibm.com]
Sent: Wednesday, June 23, 1999 7:48 AM
To: RPG400-L@midrange.com
Subject: Re: Use of DUMP in production programs, WAS: RPG enhancement
suggest on

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