Re: XML-SAX *XML_EXCEPTION event and reported parsed length question

On Fri, Jul 14, 2017 at 12:22 PM, Vernon Hamberg
<vhamberg@xxxxxxxxxxxxxxx> wrote:

I did take a shot at copying an XML to an 819-ccsid file - the characters
that did not convert were replaced with x'1A' - I didn't see an option on
the CPY command to change that - so that would need to have been changed en
masse, since THAT byte also caused a parsing error.

OK, but that seems simple enough. It's a global search and replace.
Possibly a Qshell or PASE command would be enough. At worst, you could
whip up a quick RPG program to do it, no?

I also thought, why not go for the gusto? Why not copy the original XML to a
file in CCSID37? It would make it impossible to look at the XML in any
standard editor, but maybe that wouldn't matter.

It replaced these non-convertible characters to x;3F;

Right, same thing - if it's not giving you any errors, and replacement
is what you want, you can then just replace the unwanted replacement
byte with whatever you like.

I decided I would continue as I am
with XMLTABLE - I would not easily convince anyone I should change
directions, with again, the risk factor of unknown results.

I'm not suggesting you change yet again, but part of the point of
mentioning CPY was that you could just use your original program
as-is, assuming the original program worked exactly as you wanted it
to, except for the problematic characters. Indeed, this was the
*least* risky thing to try.

John Y.