Re: Optimize *FULL

Richter,Steve wrote:

I'm still going to try to get the PAS API's to work, dammit! Even if it
kills me (which it well might - I've been sick for days, and this isn't
helping)...

you'll learn ;)   think about what the IBMer is saying at the end of this 
paragraph:

"...We recommend that API qbnAddAssociatedSpaceEntry not be used.  Instead, 
when the customer-written preprocessor is copying source statements 
from A to B, we recommend that it add whatever data it needs directly 
into the source code. ..."

Great line, but it's not clear whether this is a budgetary problem or
just a bad design.  I won't waste any more time with it.

your preprocessor can add as much code and constants as it wants to the 
module being compiled. That added code can have no effect on the running of 
the module. It is only used to store the info you want to place of the 
associated space.  You then use the debugger view APIs to create a debug view 
that excludes the added code and constants. 

Yeah, lots possibilities here.