|
I have made so many changes trying to get this to work, I'm getting lost !
Each time I make a small change, I have to use our CMS to promote the
changes to a system where I can test (which takes around 10 mins). I'm also
working on 5 other things at the same time.
I do have INZ on the DS. I also included it on the subfield. I ended up
changing it to Inz(%ucs2(' ')). This is why I get hex 20 before the
XML-INTO. After the XML-INTO, it changes to hex 4040.
The following code...
If PO(1).Header.HeaderNotes.POHdrNote(1) <> *Blanks;
...do something
...fails to see that the data is blanks.
Hex 20 is blanks in Unicode. Hex 4040 isn't ?
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jon Paris
Sent: 14 February 2012 15:58
To: Rpg400 Rpg400-L
Subject: Re: XML-INTO allowmissing=yes unicode
Have you got an INZ on the DS or individual fields? Or done a clear before
doing the XML-INTO?
Seems to me that you may be dealing with a default DS initialization.
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.
--
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.
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.