| Author |
Message
|
| kimbert |
 Posted: Thu Jun 08, 2006 5:23 am Post subject: |
 |
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| You can't force broker not to convert data in the Logical Message Tree into codepage 1208. |
Not quite true. The broker converts all character data to code page 1200 ( 16-bit characters ) not 1208. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Jun 08, 2006 5:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kimbert wrote: |
| Quote: |
| You can't force broker not to convert data in the Logical Message Tree into codepage 1208. |
Not quite true. The broker converts all character data to code page 1200 ( 16-bit characters ) not 1208. |
1200, 1208... whatever it takes...
 
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LordGladstone |
| Posted: Thu Jun 08, 2006 6:14 am Post subject: |
|
|
Novice
Joined: 07 Jun 2006
Posts: 19
|
| jefflowrey wrote: |
So let's start over with your problem. What is the value of InputRoot.MQMD.CodedCharSetId? What do you mean that the £ is getting "rejected" - is there an error message? What is it? Is this getting turned into the wrong thing? What is it getting turned into? |
The input CCSID is 819. The £ character is hex 2E. The error I get is:
Jun 8 10:15:24 e014dae0 WMQIv210[83224]: (Q.E014DAE0.1.JON_EXEC_GRP_01)[6701]"N
N413E: Attempt to Translate messages from CodedCharSetId 1208 failed. Verify that CodedCharSetId 1208 is valid and that the Message contains characters valid for this CodedCharSetId. ": Q.E014DAE0.1.90097ed5-0201-0000-0080-89adda2f12ef: IbmUtil.cpp: 207: NewUcs: :
The message then propagates to the failure queue, where the £ character is still hex 2E
I know it is the £ that is the problem, because if I use an identical message, except that the £ character is removed, no error occurs. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 08, 2006 6:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Where does this error occur? At the MQInput node?
Also, you are using WMQI 2.1? Please immediately start an upgrade process to version 6. You will be completely out of support in September. You are also running significant business risks that issues such as this will come up and you can't fix them with this version of the product. And also, 2.1 does not support XML Name spaces, so you can not do any integration with Web Services.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LordGladstone |
| Posted: Thu Jun 08, 2006 6:47 am Post subject: |
|
|
Novice
Joined: 07 Jun 2006
Posts: 19
|
The error occurs on the compute node. The £ character is in fact represented by hex A3 - as seen by running amqsbcg against the queue where the message is held. It appears as 2E in textpad.
We are aware of the end of support of 2.1 and are working on upgrading to V6 |
|
| Back to top |
|
|
| LordGladstone |
| Posted: Fri Jun 16, 2006 7:34 am Post subject: |
|
|
Novice
Joined: 07 Jun 2006
Posts: 19
|
| I have now been able to process messages containing a £ character by remving the RFH header and adding a Reset node before the main compute node. |
|
| Back to top |
|
|
|
|
