RE: XML parsing in non latin-1 environment

[Åke Olsson <ake.olsson@xxxxxx>]

Tried that and apparently UTF-16 (CCSID 1200) is more or less the only way in a multi CCSID environment such as the clients.

Thanks Scott!



This message, and/or attachment (-s), may contain confidential information. It may not be disclosed to, or used by, anyone other than the addressee. If you receive this message in error, please advise the sender immediately. Thank you

-----Original Message-----
From: Scott Klement [mailto:rpg400-l@xxxxxxxxxxxxxxxx] 
Sent: den 1 december 2015 23:23
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: XML parsing in non latin-1 environment

Åke,

If possible, update your procedure to use Unicode instead of EBCDIC.... 
  then it should work for anyone, anywhere.

-SK

On 12/1/2015 10:07 AM, Åke Olsson wrote:
> Here is the problem:
>
> We have an application that is run with same code base world wide.
>
> In this we receive - in the form of an MQ message - an XML formatted string.
>
> The application program receives the message, parses it (XML-SAX) and responds with other data in the reply-queue for the message.
>
> All this works perfectly fine, except in one environment.  One company running same application (and receiving the same datafeed) is Latvia where the receiving job runs under CCSID='1112'.
>
> Here it all breaks completely with the XML-error stated as "302" (whatever that means).
>
> I have created a "sandbox" where I have the message on and MQ-Queue, uses a browse function to read the message while leaving it on the queue and calls the parsing program.
> I have been able to verify that the only time it fails is where the receiving job is running with a non latin-1 CCSID.
>
> The question now is: What is the way around this? I have tried replacing XML-SAX with XML-INTO (using the path parameter) but the results are identical as it works brilliantly with all other CCSID:s.
>
> Med vänlig hälsning / Best regards
>
> Åke H Olsson
> Senior Consultant