So...presumably your original message contained an illegal character ( null characters are not allowed in XML documents, even in a CDATA section).
I think you have the information that you need. You need to decide whether you want the message to be
a) human readable or
b) safely processed at all times
You cannot have both.
You can choose a) and then put in some base64 decoding to make it readable - but make sure that you do the decoding after the base64 data has been extracted from the XML message. Otherwise you might as well use CDATA.
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Hence my reply earlier in this thread about catch-22 and using a Zip node to encode the errant message in a way that other (non WMB) people can recognise and decode without 'special tools'.
We used the output from the ZipNode as an attachment to an email. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Svp wrote:
If the blob is well formed XML try this
CAST(blob AS CHARACTER CCSID 850)
But what if the BLOB is not a well formed XML message? OR it contains NULL or other non escaped characters. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum