Re: Optimize *FULL

Rory Hewitt wrote:

I *think* the Program Associated Space (
http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QB3AMV00/1.3) is
something that could be used for this purpose - it does say the following
"The format of this data is specified by the user. This data will be copied
into an ILE bound program or ILE service program and is available for use
when the program is running.", so potentially you could make the program
DBGVIEW(*NONE) and also put an encrypted version of the source in the
associated space and then subsequently (when you want to debug the program)
use the QbnRetrieveAssociatedSpace API to retrieve/decrypt the source and
put it into the source member specified for the module. The
QbnRetrieveAssociatedSpace API says it should only be used by a
preprocessor, but I don't see why it couldn't be used for this purpose...

From V5R3 infocenter...

"The Retrieve Associated Space (QbnRetrieveAssociatedSpace) API is used
by a run-time routine to retrieve data stored with the
QbnAddAssociatedSpaceEntry API. This data will be placed into the
specified user space. The format of the data is specified by the user
when placed into the associated space of a module using the
QbnAddAssociatedSpaceEntry API. This API should be called only by a
preprocessor run-time routine."

I suspect they meant to say only the "Add" API should be used at
preprocessor run-time.  No good reason I can think of as to why you
can't retrieve post compile/bind.

Might be easier to just encrypt a copy of the source files (members)
instead.  As far as the location for source for debug, maybe you can
compile from qtemp.  Then for debug, you would decrypt your source into
qtemp.


Keith