× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Barbara,

Thanks for staying with this.  The compile listing is what prompted my
original post.  I didn't understand why the definitions didn't match.

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.  That seems to eliminate
some of the benefit of using externally described data structures if the
subfields don't match the files defining them. 

Other than placing the underlying fields in the data structure, what is
the benefit of externally describing a data structure if the data types
may not match?

Rick


> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
> Sent: Wednesday, March 08, 2006 12:40 PM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: Re: [WDSCI-L] Field interpreted
> differentlybetweenphysicalandlogical
>
> Rick.Chevalier@xxxxxxxxxxxxxxx wrote:
> >
> > I guess it's the explicit part I'm having trouble with.  To
> me, I don't see where I have explicitly defined anything. 
> The qualified DS is defined based on the physical file and
> the logical files used in the program are externally
> described without any redefinition in the logical DDS. 
> Again, taking it's definition from the physical file.  If
> everything is being defined in terms of the physical file why
> are the defined differently in the program?  That's what is
> confusing me.
> >
>
> Rick, anything defined on D specs is explicitly defined;
> defining an externally-described data structure explicitly
> defines the data structure and its subfields.
>
> It might help to look in the compiler listing.  You can see
> the expansion of the externally-described data structure into
> multiple D specs.
>
> --
> 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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.