Re: XML-INTO allowmissing=yes unicode

Jon <grin>

Not so fast, because I can actual emulate this behavior even though I only
has the partial code ;-)

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.

EVAL yyy:x
00000 00200020 00200020 00200020 00200020
00010 00200020 00200020 00200020 00200020
EVAL ccc:x
00000 40404040 40404040 40404040 40404040
00010 40404040 40404040 40404040 40404040


On Tue, Feb 14, 2012 at 7:07 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

On Feb 14, 2012, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

The XML-INTO is obviously mistaken the field for a G-type graphical field
where x'4040'
is a blank.

Really - I never knew that <sarcasm intended>

I thought that the OP mentioned that he got this result when the value was
_missing_ - in that case XML-INTO would not place anything in the field and
so it would not be initialized correctly unless the OP ensure that it was.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
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.