| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CCSID Message not converted using MQ 7 and WAS 7 |
« View previous topic :: View next topic » |
| Author |
Message
|
| handarto |
 Posted: Thu Jul 26, 2012 8:15 am Post subject: CCSID Message not converted using MQ 7 and WAS 7 |
 |
|
Newbie
Joined: 26 Jul 2012
Posts: 3
|
Hi,
I am using MQ 7 and WAS 7. I set queue in was 7 (resources -> queue) and set CCSID to 37. I'm expecting that when the message is put into that queue, the CCSID will change to 37. but its not working. the CCSID still 1208 (windows ccsid default). I manage to get this working by changing properties in SYSTEM.DEF.SVRCONN called 'SHARECONV' to '0'. default is 10.
Any body know why its not working? Any other solution beside changing shareconv? because I check that if we change SHARECONV to 0, there are some capability in MQ 7 is omitted.
I also try change the was version to WAS 6. and its working. maybe because its using MQ for java. but I need to use WAS 7 thats why cannot downgrade to version 6
Please Help.
Thanks, |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jul 26, 2012 8:20 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Shareconv has absolutely nothing to do with the properties of individual messages.
If you want Java to write out data in something other than UTF-18, you need to set the properties of the message or of the destination.
*exactly* why are you altering the CCSID of the sent message? Is it not being converted properly when it's read? |
|
| Back to top |
|
|
| handarto |
| Posted: Thu Jul 26, 2012 8:25 am Post subject: |
|
|
Newbie
Joined: 26 Jul 2012
Posts: 3
|
I have two application. one in iseries and one in windows (with was). so right now when the WAS send the message, I can see in the message detail that the ccsid is 1208, therefore my other application in iseries(mq also reside in this place) cannot read the message because of the format.
but if i'm using WAS 6, the ccsid is change to 37 and my application can read the message. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 26, 2012 8:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| handarto wrote: |
I have two application. one in iseries and one in windows (with was). so right now when the WAS send the message, I can see in the message detail that the ccsid is 1208, therefore my other application in iseries(mq also reside in this place) cannot read the message because of the format.
but if i'm using WAS 6, the ccsid is change to 37 and my application can read the message. |
No, it is not "because it's in 1208" that the Iseries application can't read the message.
It's because the iSeries application is doing the wrong thing, or the iSeries is not configured to properly allow message conversion.
The iSeries application should be changed to specify CONVERT when it gets the message. The iSeries should have the necessary configuraiton done to ensure that it can convert messages from 1208 - this is likely already done.
As I said, the CCSID can be set on the destination
But, again, the iSeries application is doing the wrong thing, and your code is being forced to do the wrong thing to support it. |
|
| Back to top |
|
|
| handarto |
| Posted: Thu Jul 26, 2012 8:40 am Post subject: |
|
|
Newbie
Joined: 26 Jul 2012
Posts: 3
|
| mqjeff wrote: |
As I said, the CCSID can be set on the destination |
Yes, I already set it in the WAS for the destination, the CCSID is 37. but its still not working. or this is not the correct way. I dont have the code, i only implement it, so cannot check the code. but it should be ok since its working in WAS 6 |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 26, 2012 9:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| handarto wrote: |
| it should be ok since its working in WAS 6 |
Why? If there was a bug in WAS 6 that allowed this to work (given that this behavior shouldn't have worked then either) isn't it reasonable to expect that a new release will correct that bug either accidentally or deliberately?
Only documented behaviors stay the same between versions. Unless the documentation says they've changed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
