Re: Field interpreted differentlybetweenphysicalandlogical

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

Barbara,

So, it's the QUALIFIED keyword that is causing the problem.  The purpose
of using QUALIFIED was to generate unique names that didn't conflict
with the fields in the file and at the same time identify the
origination of the field.  It sounds like using PREFIX would have been a
better choice.  Would the use of PREFIX create the same situation I have
now?

Rick

> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
> Sent: Wednesday, March 08, 2006 8:14 PM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: Re: [WDSCI-L] Field interpreted
> differentlybetweenphysicalandlogical
>
> Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
> >
> > Let's see if I understand it now.  If I define an
> externally defined
> > data structure over an existing physical file the compiler will not
> > define the numeric subfields the same as the physical file because I
> > used a D-spec.   Instead, it will use default data types
> based on the
> > data types of the fields in the physical file.  ...
>
> It's the opposite.  If you define an externally defined data
> structure, the compiler _will_ define the numeric subfields
> the same as the physical file.  If the field is zoned in the
> file, the externally-described subfield will be zoned in the program.
>
> But in your original post, your externally defined data
> structure was qualified which meant that the data structure
> didn't define the subfields that your file was using.  If you
> look in your listing, you would might something like this,
> where the = signs show the lines that the compiler generates.
>
>     Fmyfile  if    e     disk
>     D myextds     e ds              extname(myfile)
>    =D                     1    5S 0 NUM
>    =IMYREC
>    =I        S   1   5 0  NUM
>
> This program, without QUALIFIED, defines subfield NUM as 5S
> 0, and explicitly defines the NUM on the I spec.  If you add
> QUALIFIED to the definition of myextds, it would define
> MYEXTDS.NUM as being 5S 0, but it would not define the
> unqualified NUM which appears on the I spec.
>
> If you want to associate a qualified data structure with the
> fields for a file, you can use PREFIX('DSNAME.') on the F
> spec.  That way, the generated I specs will show the
> qualified names, which will match the definitions in the
> external data structure.
>
>     Fmyfile  if    e     disk       prefix('MYEXTDS.')
>     D myextds     e ds              extname(myfile)
>     D                               QUALIFIED
>    =D                     1    5S 0 NUM
>    =IMYREC
>    =I        S   1   5 0  MYEXTDS.NUM
>
> The qualified external data structure defines MYEXTDS.NUM as
> 5S 0, which fully defines the MYEXTDS.NUM on the I spec.
>
> --
> 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.