Re: Field interpreted differently between physical andlogical

Barbara,

<snip>
If you don't explicitly define the field with a D spec, the compiler will 
assign a default definition for the field.
</snip>

The I spec is created from an externally defined file.  Are you saying I need 
to go backwards and define the file internally?  That doesn't make any sense.

<snip>
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)
</snip>

How does this fit into the program though?  Is it merely to set the field 
definitions?  The data structure in the copybook is defined as externally 
described so aren't I already doing that?


In reference to Matt's post, is it the QUALIFIED keyword that is causing the 
problem?  I wanted the DS from the copybook qualified to avoid confusion 
between actual file fields and DS fields in bound programs that use the 
copybook for prototypes.

Rick

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Barbara Morris
Sent: Wednesday, March 01, 2006 5:28 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Field interpreted differently between physical
andlogical


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)

--
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) mailing 
list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.