Re: Field interpreted differently between physical and logical

Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
> 
> I've got a strange one but I'm sure there is some little thing I'm 
> overlooking.
> ...
> 366=I                             S   47   54 0I2GFID                         
>  Global Fax
> ...
> Field definition at end of compile listing
> I2GFID            P(8,0)                366D
> 

Rick, the I spec doesn't define the field, it just defines the data in
the input buffer.  If you don't explicitly define the field with a D
spec, the compiler will assign a default definition for the field.  If
it's numeric, it will be packed(*) and if it's a date it will have the
module's default date format.

(*) For maximum confusion, if a data structure has the the numeric
field's name, but no type information, then the numeric field will be
zoned, not packed.

To get all your input fields to be defined internally the same way they
are defined in the file, use an externally-described data structure in
your calling program:
   D               e ds                  extname(ISFQE201:ISFQE2R)