| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 4 matches |
| Author |
Message |
 Topic: REASON:2150 |
Pierre
Replies: 28
Views: 29471
|
 Forum: General IBM MQ Support Posted: Thu Feb 22, 2007 4:19 am Subject: REASON:2150 |
Unfortunately, if the message is a Bytes Message, then it is likely that MQMD.Format = MQFMT_NONE, rather than MQFMT_STRING.
And if MQMD.Format=MQFMT_NONE, then text conversion isn't going to happe ... |
| Topic: REASON:2150 |
Pierre
Replies: 28
Views: 29471
|
Forum: General IBM MQ Support Posted: Thu Feb 22, 2007 1:04 am Subject: REASON:2150 |
| I have tried the conversion by putting a msg containing a character with the legitimate value of the degree sign in 1208, 0xC2B0, and then getting the msg with convert to 819, and the conversion succe ... |
| Topic: REASON:2150 |
Pierre
Replies: 28
Views: 29471
|
Forum: General IBM MQ Support Posted: Wed Feb 21, 2007 4:44 am Subject: REASON:2150 |
So if you did set a ccsid of UTF-8 on the message you are running into all sorts of problems.
What happens if you don't set any ccsid and let the qmgr and client defaults handle it on the put?
... |
| Topic: REASON:2150 |
Pierre
Replies: 28
Views: 29471
|
Forum: General IBM MQ Support Posted: Wed Feb 21, 2007 2:36 am Subject: REASON:2150 |
Hello,
I work with Julia and followed her issue almost from the beginning.
Julia, If your application is java, do not set any ccsid.
The qmgr should handle it with the default settings.
I agre ... |
|
|
|
