| Author |
Message
|
| eaistudent |
 Posted: Fri May 30, 2014 7:19 am Post subject: EBCDIC to ASCII data conversion using WMB msg flow |
 |
|
Newbie
Joined: 30 May 2014
Posts: 1
|
Hi,
Im receiving an EBCDIC file from a legacy system with Special characters. The input MRM msg being read into MB has a CCSID of 500.
We are trying to parse the MRM into an xml msg as shown in the code snippet below -
SET target.MQMD.CodedCharSetId = 819;
SET target.MQMD.Encoding = 546;
SET target.XMLNSC.Company = source.MRM.DATA.NAME;
SET target.XMLNSC.Department = source.MRM.DATA.DEPARTMENT;
But the input data is getting corrupted when its being parsed by MB. I have verified the below using the user trace.
Input to MB was ‘F PÈRRAULT Z’ –
MB read it as 'F PþRRAULT Z'
Input to MB was ‘ATTORÑEY AT LAW Z’ –
MB read it as - 'ATTORµEY AT LAW Z'
I have tried casting the input data as a character with & without the CCSID 500 just to check if the ebcdic data is getting parsed unchanged. But the issue is that the input data is getting changed.
How can this be avoided? (I dont want to change the CCSID of the Queue Manager.) |
|
| Back to top |
|
 |
| ganesh |
| Posted: Fri May 30, 2014 12:02 pm Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| The CCSID is unable to handle the characters. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri May 30, 2014 1:31 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Make sure the MQinput node has convert option unchecked.
Make sure the input message has valid characters for CCSID 500.
WMB will convert internally to CCSID 1200.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat May 31, 2014 3:00 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Change your target CCSID to a value that can handle all the special characters (like UTF-8 or 1208 ).
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jun 02, 2014 6:29 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| But the input data is getting corrupted when its being parsed by MB |
That is extremely unlikely. As others have said, check that the CCSID on the input message correctly describes the content of the input message. Then check that the contents of the message tree look corrrect ( use a Trace node with pattern ${Root} to do this ). Finally, carefully select an output CCSID that is able to represent all of the characters in the message tree. UTF-8 or UTF-16 are both good choices because they can represent all Unicode characters.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
|
|
