×
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.
Hi Dennis - it is certainly the "unreferenced" issue as the test in
the thread I referenced demonstrated.
When the READ is targetting a DS directly all fields are always moved
because there are no field moves generated - the whole record is moved
as a lump. Although this can't always be true in the case of EXFMT and
a *ALL defined DS.
The issue seems to be under what circumstances a DS that consists of
fields from a record will be populated by a read that does _not_
specify the DS as the result. The code in the referenced thread
appears to show that the fields in an externally described DS will not
be populated unless referenced elsewhere. Michael is convinced that if
the field names are specified "by hand" that they get populated - and
that's what I still have to test.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
On Jul 2, 2010, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
Jon, I believe this is related to age-old "unreferenced fields"
idiosyncrasy. Even as far back as the System/3, the RPG compiler
has always
removed fields that are unreferenced (RNF7031 "errors"). ...
*BUT* I don't know what
happens when the READ is to a data structure. Seems to me at that
point
that the fields should be populated. If they're blank in that
scenario,
then it seems to me that either there's mystery happening and the
READ-INTO-DS doesn't work like it appears to be designed (which I
doubt), or
the compiler is wiping the unreferenced fields (which I also doubt).
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.
midrange.com
