| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Getting non-readable characters on mainframe queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ajit |
 Posted: Thu Mar 31, 2005 4:36 pm Post subject: Getting non-readable characters on mainframe queue |
 |
|
Newbie
Joined: 14 Apr 2004
Posts: 8
|
We have a point-2-point connection of a distributed queue manager with mainframe queue manager. No WMQI invlolved.
The putting application (VB6) is setting the CCSID as 500 and encoding as 785. Still, when the message reaches the MF queue, the data is all in non-readable characters. We tried with the CONVERT parameter of the sender channel with YES as well as NO. In both the cases, result was the same.
Any ideas what can be done in such a case ?
Thanks. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Mar 31, 2005 5:30 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, the first thing I would tend to do is refer back to the manuals to make sure I understood what setting CONVERT on the channel did or did not do.
Then I would make sure that I understood Conversion to know what data will be converted, and what data won't be converted.
And then I would change the code to indicate that the data is String data, and to specify CONVERT on the Get rather than in the Channel.
But that last bit is only useful if you've done the first bit already.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kman |
| Posted: Thu Mar 31, 2005 10:59 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
| And I would not, normally, set the CCSID and encoding on my put. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Apr 01, 2005 3:56 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| jfluitsm |
| Posted: Tue Apr 05, 2005 12:37 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
The ccsid on the put must reflect the charset used to create the message. For VB6 I believe this is utf8 (ccsid 1208) otherwise it is Windows Latin 1 (ccsid 5348).
What you did is creating a message in one of the above charsets but telling MQ that it is in EBCDIC.
The conversion should be done preferably on the receiving site using the MQGMO_CONVERT option or on the channel. The message itself must be all text and the MQMD.Format must be MQFMT_STRING in order to get the conversion working.
For your mesage the encoding doesn't play a role, in general ther is no need to change the encoding.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| 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
|
|
|
|
