Re: NOOPT D-Spec keyword

Bill,   If the fields in question were in the PSDS or INFDS then the problem
is the one which I related, which is documented in the RPG reference under
the NOOPT D-spec keyword.  In this case you can place the NOOPT keyword on
the those data structures, or their subfields, and the problem should be
solved.  Nevertheless, both Hans and Bob Cozzi have said that *FULL
optimization doesn't buy you anything meaningful, so the exercise is
essentially academic.
    -Dave K         ps - Thanks Hans !

----- Original Message -----
From: <bill.reger@convergys.com>
To: <rpg400-l@midrange.com>
Sent: Tuesday, June 18, 2002 9:59 AM
Subject: Re: NOOPT D-Spec keyword


>
> Hans,
>
> I must admit that your email is way over my head and it's very possible
I'm
> not at all on the same page with you.  But is the situation you are
> describing responsible for some bizarre behavior I recently saw?
>
> Just before distribution, I always create my WRKDBF objects (RPG ILE and
CL
> ILE, no OPM's) with *FULL optimization.  And then I remove observability.
> The idea being to make the objects as small and as efficient as possible.
>
> When I tested out everything I started seeing blanks, zeros, and other
> strange values in fields that I knew were not.  After scratching my head
> for a long while, on a hunch, I recreated everything with optimization
> *BASIC.  Magically (and mysteriously) WRKDBF started behaving properly and
> showing field values accurately.
>
> I may never use *FULL optimization again after this.  Is this soemthing
> that is "known" behavior?  Or I am just not understanding optimization?
>
> Bill