Re: Regarding retrieving source from modules

Gary wrote:
>...
>I could probably list more, but I think you see the point. My personal
>opinion is that there is only one acceptable reason, for all practical
>purposes, to not have DBGVIEW(*LIST) on an object. That is when you are
>distributing software and don't want it "visible" to the outside world.
>And, I'm of the opinion that it might be a good idea to have a change
>management system that actually retrieves the source from the object any
>time it is being worked on.

I think you've argued quite effectively for the need for using
a good change management system.  I certainly don't disagree
with you on that.

But, just as I think that the dbgview(*list) is a poor substitute
for proper backup and recovery procedures, I think it's also a
poor substitute for proper change management procedures.

Here's one argument against using dbgview(*list) to recover the
source for a particular version of your software:  All of your
/copy members get folded together with your main source.  You've
now lost the benefits of using /copy members.

Cheers!  Hans

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


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---