Re: Optimize *FULL

["Rory Hewitt" <roryhewitt@xxxxxxxxx>]

Keith,

Indeed. As an initial trial method, I'd probably define the program with
DBGVIEW(*SOURCE) and then run my utility to create a
temporary library/file/source member, decrypt the source from the PAS and
copy it into the source member, run debug and then at the end, delete the
source member. Probably have some basic authority checking on the temporary
source member - maybe an exclusive lock to disallow anyone else copying the
source or something like that....

The only other option would be to write my own debugger which can directly
access the encrypted source.

Rory


On 1/10/07, Keith Carpenter <carpcon@xxxxxxx> wrote:
> Rory Hewitt wrote:
> > 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...
>
> Looking at the Retrieve API, it uses "call level" to identity the
> module's associated space.  Sounds like it should work for both programs
> and service programs.  great.
>
> I would assume you'd use your retrieval tool while the application is in
> use but before starting debug.
>
> Novel idea.