Re: Error with XML-INTO caused by non-printable characters

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Do we have a new club? Seems these days there is also a JSON club, more 
people are joining it!

Sorry, Jon, couldn't resist!

Cheers
Vern

On 2/24/2021 5:22 PM, Jon Paris wrote:
> Why are you writing it to the IFS?  Why not just have XML-INTO directly decode the XML club?  For that matter use SQL to process the XML in the club directly.
>
> Reason for saying this is that it seems to me that by copying data to the IFS that you are introducing extra steps that could insert oddball characters if there are any code page issues along the route.
>
> Can you post some of the troublesome XML ?
>
>
> Jon Paris
>
> > On Feb 24, 2021, at 3:09 PM, Carel <coteijgeler@xxxxxxxxx> wrote:
> >
> > Runnin on V7.1
> >
> > We receive from a SAP environment xml documents which are stored as a CLOB in a PF on our system.
> >
> > To process those xml documents we extract those documetns from that file, store it on the IFS and then read the IFS file in with XML-INTO.
> >
> > Some of those xml documents crash on the XML-INTO opcode. It appears those xml documents contain non-printable charaters (less than x'40')
> >
> > So, we have to remove those non-printable charaters.
> >
> > I looked at QSH -tr command, but could not gget it to work.
> >
> > Another option is using SQL when retrieving the CLOB from the PF before writing to the IFS.
> > Itried the following syntax:
> >
> > exec sql
> > select REPLACE(CLOB_in_PF, x'0102 ... 3E3F', '') into :SQLCLOB_field from Our_PF ;  (thus all hex values with the exception of NULL).
> >
> > This doesnot work.
> >
> > Question:
> > How can we remove those non-printable characters from an xml document stored in our PF?
> >
> > TIA
> >
> > Kind regards,
> > Carel Teijgeler
> >
> >
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at https://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
> >
> > Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com