| Author |
Message
|
| kdorre |
 Posted: Wed Jan 21, 2004 4:18 pm Post subject: AS400 to W2k character conversion |
 |
|
Novice
Joined: 17 Jul 2002
Posts: 15
Location: New Zealand
|
Hello
Thanks in advance for any help.
We are having a problem where an MQ Get from a W2K PC to an AS400 is not translating the data to a readable format on the PC.
our setup is
1 AS400 MQSeries 5.2 Server
2 Win 2K pc running application built with 5.3 Client libraries.
3 The client application has the following set for the GET call
gOptions = MQGMO_WAIT | MQGMO_FAIL_IF_QUIESCING | MQGMO_CONVERT | MQGMO_SYNCPOINT;
When we browse the message using the IBM supplies amqsbcg (from the PC) we get the following
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 37
Format : 'MQSTR '
Priority : 0 Persistence : 1
and the data in the message buffer is garbled like this
ÙÁÒÙðñÃÖòñóñ÷÷âÙKƒ¢¥%.....
is there anything here that we are missing or required to set?
Once again thanks in advance for any help
Regards,
Keith
_________________
life, liberty and the persuit of happiness |
|
| Back to top |
|
 |
| EddieA |
| Posted: Wed Jan 21, 2004 5:39 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Are the messages not translated in your application.
They aren't translated by amqsbcg because that doesn't use the GMO_CONVERT option.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kdorre |
| Posted: Thu Jan 22, 2004 11:30 am Post subject: |
|
|
Novice
Joined: 17 Jul 2002
Posts: 15
Location: New Zealand
|
Correct the application is not translating the message when it is taken from the queue to the PC.
Just for for future reference can anyone explain how the encoding field matches up with the CCSID field?
_________________
life, liberty and the persuit of happiness |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 22, 2004 12:36 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kdorre wrote: |
| Just for for future reference can anyone explain how the encoding field matches up with the CCSID field? |
My understanding is that Encoding is for numbers and CCSID is for characters.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kdorre |
| Posted: Thu Jan 22, 2004 2:02 pm Post subject: |
|
|
Novice
Joined: 17 Jul 2002
Posts: 15
Location: New Zealand
|
| Quote: |
| My understanding is that Encoding is for numbers and CCSID is for characters. |
So I see in the documentation that Windows support CCSID 037 but in the list of supported code sets there is no mention or reference to 237 could that be my problem?
the documentation I refer to is the programmers reference guide, appendix H, unicode conversion support
Regards, Keith
_________________
life, liberty and the persuit of happiness |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Jan 22, 2004 6:08 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
No. 237 is the Encoding, which refers to how numbers are stored. Little endian, big endian, S/390 Floats, etc. This has nothing to do with character conversion.
OK, check the following, because there doesn't seen to be enough spaces after MQSTR in what you pasted in earlier. This field must be MQSTR followed by either a null, or the field padded with spaces. Can you use the MQExporer to view the message. That *will* convert a message type of MQSTR if you click the Text radio button. If the button is greyed out, then it didn't recognise the MQSTR.
Also check the logs on the machine where the application was run. If MQ tried to convert and got a failure, then it should log something. If there was a conversion failure, then the application should have got a "Warning" return code back, not a zero. Is the application checking for that.
Lastly, when you run amqsbcg, post the first couple of lines exactly as output.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| mrlinux |
| Posted: Fri Jan 23, 2004 1:20 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
This is a long shot, but the mqmd.format field is an 8 byte field and must
3 spaces after the MQSTR.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
|
|
