Re: You know, I'm pretty sure it's zoned...

On Wed, 6 Feb 2002, R. Bruce Hoffman, Jr. wrote:
> >
> > Just out of curiosity, what would the programmer's EXPLICIT INTENT be if
> > the DDS for the display file was defined as "10Y 0"?
> >
> > How about "10N 0"?  Should RPG transform that one to packed?  Or maybe
> > you'd like it to be transformed to indicators?
>
> You mean the edit codes???? Not the data type?
>

No...  my understanding of your rant was that a field defined in DDS like
this:
    A            FLD001        10S 0B  1  3

should be mapped to a zoned decimal field in RPG.  (i.e. "10S 0" in RPG)
because the programmers "explicit intent" was to define it that way.

So, what I'm asking is, if you instead defined it as:
     A            FLD001        10Y 0B  1  3
or
     A            FLD001        10N 0B  1  3

What should the compiler assume that the programmer's "explicit intent"
is?

This is not the same as an edit code -- at least to me.   The same
field with an edit code would look like this:
     A            FLD001        10Y 0B  1  3EDTCDE(M)

The problem is... in DSPF DDS "10S 0" means "10,0 with a keying option of S"
all numbers are zoned decimal, because packed & integer are not
human-readable.