Re: Eval-corr

On 13 May 2013 06:23, Florin Todor wrote:

<<SNIP>> my work-around was this:

if DS_HRESD01.D1CHGAMT < 0;
DS_DETD01 *= (-1);
endif;

and it worked. So, the subfield DS_HRESD01.D1CHGAMT is recognized as
a negative value;

While I was originally going to describe the effect for the presentation by debug as "disturbing" [the term /interesting/ is far too complacent sounding toward the debugger; just look at the confusion it caused], I would find the above claim for the effects from the RPG comparison to be even more disturbing... if I understand correctly.

Does that claim imply that the 12 byte string [with character b representing blanks] 'bbbbbb-79349', when stored in a zoned decimal variable, will compare as less than a zero value? Please tell me that is not so!

Regards, Chuck

Barbara Morris on Friday, May 10, 2013 8:36 PM wrote:

On 5/10/2013 9:56 AM, Florin Todor wrote:

ds_hresD01 = f_in210txt;
// DS_HRESD01.D1CHGAMT = -793.49 <---- from Debug session
eval-corr ds_detD01 = ds_hresD01;
// D1CHGAMT OF DS_DETD01 = 0000000793.49 <-- from Debug session

That's interesting that the debugger shows the zoned value that
way. If that '-' character happened to be '/', the debugger would
show the value of DS_HRESD01.D1CHGAMT as /793.49. <<SNIP>>