Re: Field interpreted differentlybetweenphysicalandlogical

Rick.Chevalier@xxxxxxxxxxxxxxx wrote on the
Websphere Development Studio Client for iSeries  (WDSCI-L) mailing list:
> 
> 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?
> 

(This was formerly a thread on the WDSCI-L mailing list.)  Here's a link
to the thread index for anyone who wants to catch up on it:
http://archive.midrange.com/wdsci-l/200603/threads.html#00012 (the
logical thread shows up as several individual little threads.)

Rick, using PREFIX would have caused the same situation.  In that case,
your file would have been using the unprefixed names, while the data
structure defined prefixed names.

The purpose of the data structure in the /copy file is to define other
fields and parameters used in the /copy file.  I don't think it
shouldn't have a secondary purpose of being available for program data.

I think the correct fix is to define the externally-described data
structure that your program needs in the source for your program, and
not to care that it is also defined in the /copy file.  If you're
worried about the extra physical storage allocated for the data
structure in the /copy file, you could define it as BASED (and then
don't set the basing pointer to point to anything).

I think your original purpose was good; generating unique names that
didn't conflict with the fields of the file.  Now you're trying to both
have and not have the fields in the data structure the same as the
fields in the file; if you change the /copy file to be unqualified and
unprefixed for this one program, you will have a problem later if you
copy it into a program where you _don't_ want the same names.  And
there, the fix will be much harder than the fix for this program of
adding its own definition of the ext data structure.