Re: XML-INTO allowmissing=yes unicode

Sean,

Just created a similar program on 7.1 (took an existing program and
changed subfields to UCS-2). Result: prior to XML-INTO all fields are
(just as in your program) initialized to x'0020'; after XML-INTO missing
fields still contain x'0020'. Seems like a bug that has been solved in
7.1; maybe you need a PTF.

Joep Beckeringh


rpg400-l-bounces@xxxxxxxxxxxx wrote on 14-02-2012 12:24:28:

McGovern, Sean

IBM i 6.1.
I have a XML document on the IFS. CCSID is 1208.
A cut-down version of the file may be...

<?xml version="1.0" encoding="UTF-8"?> <PURCHASEORDER> <HEADER>
<HEADERNOTES> </HEADERNOTES> </HEADER> </PURCHASEORDER>

...this structure is defined as follows...

<PURCHASEORDER> <HEADER> <HEADERNOTES> <POHDRNOTE></POHDRNOTE> </
HEADERNOTES> </HEADER> </PURCHASEORDER>

In the RPGLE, this is defined as follows: -
D PO DS Qualified Inz
D Dim( POIdxMax )
D Header...
D LikeDS( Header_t )
D Header_t...
D DS Qualified
D Based( Template )
D HeaderNotes...
D LikeDS( HeaderNotes_t )
D HeaderNotes_t...
D DS Qualified
D Based( Template )
D POHdrNote...
D 50c Inz
D Dim( POHdrNteIdxMax )
read as follows...

options = 'doc=file + path=Update/member/PurchaseOrder
+ case=any + allowextra=yes
+ allowmissing=yes';
xml-into PO %xml( xmlfile : options );

When the POHdrNote data is not present in the XML, I expect the PO
(x).Header.HeaderNotes.POHdrNote(x) data field to contain blanks.
However, when I look at the hex values of the field in debug, the
hex value is all 40s (I would expect hex values of all 20s for unicode

?).

When I test in the program whether the data is *Blank, the test
gives me the wrong result.
Why am I getting hex value of 40s rather than 20s when the data tags
are missing from the XML ?
Thanks.