| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| REPLACE(ing) CRLF with a literal string of "<br>& |
« View previous topic :: View next topic » |
| Author |
Message
|
| jjordan |
 Posted: Tue Jul 14, 2009 3:33 am Post subject: REPLACE(ing) CRLF with a literal string of "<br>& |
 |
|
Novice
Joined: 14 Oct 2005
Posts: 17
Location: Portland, ME
|
I get external data pumped through my message flow that contains CRLF characters (X0d0a) in a node of my XMLNSC message tree. I need to replace them with a literal string of '<br>'. I've tried several methods, including changing the message to a BLOB, replacing that characters, and then trying to convert the message back to XMLNSC (which has other issues, because of CRLF's located otherwhere in the XML stream that I DON'T want to convert.
I finally declared a character literal in the ESQL as this:
declare sCRLFLiteral '
';
I don't like it, BUT it appeared to work (mostly).
Now for the rest of the dilemma - the CRLF's are being generated in a Windows worlds, and sent to a Linux server, where a newline is simply a LF. The CR (\r) is left untouched by the REPLACE function.
Does anybody know of a more effective method to replace CRLF's? And, does anybody know how I can remove the CR?
Thanks for your help.
Jeff |
|
| Back to top |
|
 |
| jbanoop |
| Posted: Tue Jul 14, 2009 5:24 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
| I thought that if the character code set id and the encoding in the incoming MQ message (assuming your input is MQ) had the unix values, the broker parsed the message accordingly ? |
|
| Back to top |
|
|
| jjordan |
| Posted: Tue Jul 14, 2009 9:31 am Post subject: |
|
|
Novice
Joined: 14 Oct 2005
Posts: 17
Location: Portland, ME
|
Thanks for the input - I followed you're idea, and changed the CCSID on the incoming message, and all was well.
I haven't worked much with CCSID's, so I hadn't thought to look there.
The incoming messages came from a Windows based MQ queue (passed through a remote queue to the Linux based MQ queue). MQ Broker picked the message up and processed it.
In the processing, I changed the CCSID from 1252 (??I think??) to 923, and all worked well!
Thanks again!
Jeff |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
