| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CCSID problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| sarat |
 Posted: Thu Jun 06, 2013 6:54 am Post subject: |
 |
|
Centurion
Joined: 29 Jun 2005
Posts: 136
Location: India
|
Hello All,
We are now facing with similar error. We have an issue at customer side for CCSID.
We have special characters (Umlaut) in the incoming message with CCSID 850. But in our all Envs CCSID is 1208 and it was the same case at the customer before 2 weeks.
But since last week all message logs in ESB (WMB) contains CCSID 850. Even inside WMB also there is no special setting. Broker is just carrying the same properties across the flow.
We got a confirmation that default QMGR CCSID for partner system and ESB QM also 819.
Where could be the possibility to over writing the CCSID !!
As per above suggestions, now requested for code page for AIX machine and also Channel STATUS (If it is YES , CCSID will be taken over of OS CCSID).
looking for any other suggestions !!
_________________
With Regards,
Sarat. |
|
| Back to top |
|
 |
| sarat |
| Posted: Mon Jun 10, 2013 5:38 am Post subject: |
|
|
Centurion
Joined: 29 Jun 2005
Posts: 136
Location: India
|
I don't know the reason why my post was detached from the other thread.
@ All : I was referring to this post
http://www.mqseries.net/phpBB2/viewtopic.php?t=63405
@ Admin/Mod : Even, If some wants to help also they cannot as there is no reference what I'm taking about !!
_________________
With Regards,
Sarat. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Mon Jun 10, 2013 10:55 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| sarat wrote: |
| We have special characters (Umlaut) in the incoming message with CCSID 850. But in our all Envs CCSID is 1208 and it was the same case at the customer before 2 weeks. |
So, the customer used to send messages with ccsid=1208, and now it's sending messages with ccsid=850? If that's the problem, then check the customer application, and make sure it sets the message ccsid as needed, before it puts the message on a queue.
| sarat wrote: |
| But since last week all message logs in ESB (WMB) contains CCSID 850. Even inside WMB also there is no special setting. Broker is just carrying the same properties across the flow. |
Otherwise, the message flow can convert the incoming message either at the WMQ level, by enabling "Convert" in the MQInput node, or better yet at the WMB level, depending on the parser, by setting the OutputProperties ccsid.
| sarat wrote: |
| We got a confirmation that default QMGR CCSID for partner system and ESB QM also 819. |
If the desired ccsid is 1208, then it's best that the message flow specify that, instead of depending on the default qmgr ccsid. |
|
| Back to top |
|
|
| sarat |
| Posted: Wed Jun 12, 2013 3:16 am Post subject: |
|
|
Centurion
Joined: 29 Jun 2005
Posts: 136
Location: India
|
Hi rekarm,
Thanks for the response !!
| Quote: |
| So, the customer used to send messages with ccsid=1208, and now it's sending messages with ccsid=850? If that's the problem, then check the customer application, and make sure it sets the message ccsid as needed, before it puts the message on a queue. |
It was confirmed that other application sending the CCSID 1208. We stopped the channel and had a check in Transmission queue.
| Quote: |
Otherwise, the message flow can convert the incoming message either at the WMQ level, by enabling "Convert" in the MQInput node, or better yet at the WMB level, depending on the parser, by setting the OutputProperties ccsid. |
We are not using this as request should be send to another aplication which also looking for 1208 CCSID.
| Quote: |
If the desired ccsid is 1208, then it's best that the message flow specify that, instead of depending on the default qmgr ccsid. |
This is a work around already we have it in our mind. But, we just want to know the root cause of issue.
_________________
With Regards,
Sarat. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 12, 2013 3:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So how do you know that anything is in 850?
Where are you seeing the CCSID of 850? |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu Jun 13, 2013 3:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| sarat wrote: |
| But, we just want to know the root cause of issue. |
The root cause of what issue, exactly? Please describe more clearly at which two points the messages switches from ccsid=1208 to ccsid=850. If there's an unwanted conversion between those two points, then that would be the place to disable it. |
|
| Back to top |
|
|
| sarat |
| Posted: Thu Jun 13, 2013 4:36 am Post subject: |
|
|
Centurion
Joined: 29 Jun 2005
Posts: 136
Location: India
|
| Quote: |
So how do you know that anything is in 850?
Where are you seeing the CCSID of 850? |
In the log queues and once it reaches to Broker.
| Quote: |
| The root cause of what issue, exactly? Please describe more clearly at which two points the messages switches from ccsid=1208 to ccsid=850. If there's an unwanted conversion between those two points, then that would be the place to disable it. |
Earlier suspected it was CRM application which was sending 850. But as explained before, it was 1208 before reaching to broker QM.
Yesterday , we got a clue about this. It seems customer using third party tool (like MQJ , MO71) to write the messages to attach in the defects. I will update here once we get the information .
_________________
With Regards,
Sarat. |
|
| 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
|
|
|
|
