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

That was the basic idea of my suggestion, though I would recommend
against 819 (no need to be that restrictive).

Okay, there are a lot of CCSID alternatives to pick from.

I actually thought this
was merely a minor variation on your original filtering suggestion.
But it would seem XMLTABLE happens to provide both filtering and
parsing, which is an unbeatably attractive proposition for Vern (and
I'm sure for many folks).

Running the CPY command just prior to the XML-SAX opcode is quite trivial.

He seems to be happily going down the
XMLTABLE path now; I see no reason to try to pull him off it at this
point.

I'm not vested in XML-SAX or XMLTABLE, but Vern has sent some mixed
signals. First that XMLTABLE would mean a problematic rewrite, then later
he "saw the light", which I took to mean that he viewed XMLTABLE as the
better option.

In regard to "a problematic rewrite", Vern indicated that 13 tables would
be updated from the XML file, which seems somewhat relevant.