Re: Optimize *FULL

Jon,

A good point - I will look into doing this. Also, I've been experimenting
with including an encrypted copy of the program source in the Program
Associated Space, which is yielding good results also...

As to Crispin's subsequent comment, all I can say is "Ain't. Gonna.
Happen."...

Rory


On 1/10/07, Jon Paris <Jon.Paris@xxxxxxxxxxxxxx> wrote:

>> However, using DBGVIEW(*LIST) (or DBGVIEW(*ALL), for that matter) goes
against everything that Aaron (like me) is trying to do - to make his
production objects (which he ships to *external* customers) more secure.

No argument - but in order to debug when you use *SOURCE you have to put
the
source on the target machine.  I would argue that that is even less
secure.
The scenario I would propose is to:

a) Compile with *LIST
b) Produce copy of *PGM for distribution
c) Remove debug capability completely from the copy
d) Ship the copy
e) In the event that I need to debug on the production system copy the
debug-
able version to the system.
f) When debugging complete reinstate the no-debug version or (simpler)
remove the debug capability from the production copy.

Surely this is safer than having a source on the production box?  The only
potential exposure of my code is during the period when I'm actively
debugging and someone would have to know how to resurrect a source from
the
debug-able version of the program.


Jon Paris
Partner400
www.Partner400.com