Author |
Message
|
ramprasath_kumar |
Posted: Tue Jul 03, 2007 4:52 am Post subject: MQGET with Conversion |
|
|
Newbie
Joined: 03 Jul 2007 Posts: 4 Location: INDIA
|
Hi,
Can u get me the values i can use for
MQMD-encoding
MQMD-codedcharsetid
MQMD-format
Im issuing an MQGET call through a program running in IMS region, in MF.
i want to get a message from the queue, which is in unicode(utf-16) format.
Regards,
Ram |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jul 03, 2007 4:55 am Post subject: Re: MQGET with Conversion |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
ramprasath_kumar wrote: |
MQMD-encoding
MQMD-codedcharsetid
MQMD-format
|
These values are set on the put not the get, and should match those of the originating platform/message (typically those of the queue manager).
Provided you have relevant conversion tables on the receiving end, string messages should be automatically converted. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
zpat |
Posted: Wed Jul 04, 2007 3:28 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
MQGMO_CONVERT is wha you need on the MQGET.
Only works if the message has MQMD.Format = MQSTR |
|
Back to top |
|
 |
platform_guy |
Posted: Fri Nov 09, 2007 8:19 am Post subject: CODEDCHARSETID |
|
|
Newbie
Joined: 09 Nov 2007 Posts: 4
|
Hi,
I’m receiving data from a Sun box that support Multilingual. The CCSID on their side sides appears to be 819 or 437 to support several European languages. My question is should I set the CCSID on my side to match there and would it work or is there something else that needs to take place. The CCSID on the QMR is turn off.
Thanks |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Nov 09, 2007 8:39 am Post subject: |
|
|
Guest
|
Quote: |
Only works if the message has MQMD.Format = MQSTR |
Works, too, if there is a conversion utility named in the Format field; AND the format utility exists on the receiving end of the channel.
Support pac MA07 is a white-paper on data conversion - a good place to start. |
|
Back to top |
|
 |
zpat |
Posted: Sat Nov 10, 2007 12:37 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
The mainframe QM CCSID should be 500 or some other EBCDIC value. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Nov 28, 2007 5:57 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
jefflowrey wrote: |
2019 is NOT a character conversion issue. |
As has been said before, like here:
http://www.mqseries.net/phpBB2/viewtopic.php?t=40768
I stand by the advice I gave here.
jefflowrey wrote: |
Please STOP posting in threads that aren't your own. |
This is good advice as well. Especially when the threads are not connected to your problem!  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
platform_guy |
Posted: Wed Nov 28, 2007 8:45 am Post subject: |
|
|
Newbie
Joined: 09 Nov 2007 Posts: 4
|
Sorry, you are correct...the 2019 is/was not my focus... the focus was trying to convert é, è ù, à ç or ü, ä, ö, ° when being passed from the Unix to the MF... in setting the CCSID to 819 on Unix and 500 on the MF the data was being converted.
Thanks |
|
Back to top |
|
 |
|