|
On 10/2/2017 3:13 PM, James H. H. Lampert wrote:
Any idea why this would happen?
Possibilities:
A skipped/unsuccessful CHAIN (wrong indicators have stung me)
An extra CHAIN to a different (child/parent?) record that inadvertently
resets the field contents
Updating in one library, querying from another (test/QA/production)
Data structure reuses some of the fields, but is referred to only under
certain conditions (this one is particularly insidious, and has lead me
to always refer to the compiler cross reference listing to make 100%
certain the fields in question have only the two references I think they
have)
--
--buck
THIS is the work for which matching record is the proper tool.
And I am unanimous in that.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
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.