| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 5 matches |
| Author |
Message |
 Topic: Character set 1200 doesn't work whereas 1202 works |
pallavi570
Replies: 17
Views: 40629
|
 Forum: IBM MQ API Support Posted: Thu Aug 25, 2016 10:27 pm Subject: Re: Character set 1200 doesn't work whereas 1202 works |
I found that the MB has been upgraded from 7.0.0 to 7.0.1, ...
There is no MB v7.0.1, so that's not right. There is an MQ v7.0.1, but it might have made more sense to upgrade to a newer version, at ... |
| Topic: Character set 1200 doesn't work whereas 1202 works |
pallavi570
Replies: 17
Views: 40629
|
Forum: IBM MQ API Support Posted: Wed Aug 24, 2016 3:34 am Subject: Re: Character set 1200 doesn't work whereas 1202 works |
Can anyone please help me in understanding whats the difference between 1200 and 1202 and what worked with 1202.
Use some sort of debug tool (such as amqsbcg, q, rfhutil, etc.) to examine the message ... |
| Topic: Character set 1200 doesn't work whereas 1202 works |
pallavi570
Replies: 17
Views: 40629
|
Forum: IBM MQ API Support Posted: Tue Aug 16, 2016 8:28 am Subject: Character set 1200 doesn't work whereas 1202 works |
MQ data conversion is dependent on the CCSID of the message itself.
Perhaps the version of .NET changed, which changed the default CCSID, but the MQ Message still had the old CCSID.
will the def ... |
| Topic: Character set 1200 doesn't work whereas 1202 works |
pallavi570
Replies: 17
Views: 40629
|
Forum: IBM MQ API Support Posted: Tue Aug 16, 2016 7:16 am Subject: Re: Character set 1200 doesn't work whereas 1202 works |
Can anyone please help me in understanding whats the difference between 1200 and 1202 and what worked with 1202.
The Endian position. See
Thanks for your inputs.
But it worked earlier with 120 ... |
| Topic: Character set 1200 doesn't work whereas 1202 works |
pallavi570
Replies: 17
Views: 40629
|
Forum: IBM MQ API Support Posted: Tue Aug 16, 2016 7:05 am Subject: Character set 1200 doesn't work whereas 1202 works |
We had a issue in the .Net application wherein by default character set value was being sent as 1200 to WMQ which wasn't being processed with reason XML Parsing errors at Message Broker end.
Whereas ... |
|
|
|
