This morning I can confirm that all seems good in the world.
Many thanks to everyone for their help and patience.
As noted previously, I was using an incorrect version of the /copy XML DS member. This didn't have an INZ keyword to initialise the fields.
I can confirm now that when using the INZ keyword on the DS, the before XML-INTO and after XML-INTO values are now as expected.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: 14 February 2012 23:14
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: XML-INTO allowmissing=yes unicode
On 2/14/2012 2:47 PM, Henrik Rützou wrote:
This is more likely a data structure behavior problem because a
unicode fields starts it's "life" with complete different values based
on whether they are defined as a free field or in a data structure.
I think the whole problem has been that the data structure started out with the standard RPG value for an uninitialized data structure, and never got changed from that. It is standard RPG behaviour to initialize a data structure with no INZ to x'40's, no matter what type of subfields there are.
Sean has already said that there are two versions of the data structure in the /copy file, and that the one without INZ was being used.
Sean had intended to have the data structure initialized, and was operating on the assumption that it was initialized. If it had actually been initialized as intendend, I'm sure that there wouldn't have been this apparent problem with XML-INTO.
But maybe it's good that it didn't, because on the systeminetwork version of this thread, I was able to tell Sean about how using the countprefix option is a much better way of handling missing XML data than the allowmissing option.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.