| Author |
Message
|
| sac063 |
 Posted: Sun Nov 21, 2004 1:52 am Post subject: Problem with CCSID conversion |
 |
|
Apprentice
Joined: 23 Jan 2004
Posts: 36
|
Hi All,
We have a message brokering service on windows system that integrates several unix and z/OS systems. The tranpost layer for the broker is Windows MQ 5.3 with CSD 07. One of the point to point connection is where the broker receives the message from a mainframe-1 (CCSID 1047) without CCSID coversion and has to route the message to another mainframe-2 system (CCSID 500).
Mainframe-1 --> Windows --> Mainframe-2
I have set the conversion option to YES on the sender channel to mainframe-2 system. But the messages are ending up in the DEAD LETTER QUEUE and the logs show that Windows MQ cannot convert from CCSID 1047 to 500. I am aware that if the message reaches in the windows CCSID (437) format then it can be converted to 500. But it will reach Windows with CCSID 1047 as it cannot be converted on Mainframe-1 system or on the channel to Windows system.
Is there any option to convert the message from 1047 to 500 in the MQ layer without using the broker services ?
Any information would be very helpful 
Thanks. |
|
| Back to top |
|
 |
| Nizam |
| Posted: Sun Nov 21, 2004 6:43 am Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
| Try using MQGMO_CONVERT in your get message options in your get program. |
|
| Back to top |
|
|
| sac063 |
| Posted: Sun Nov 21, 2004 11:06 am Post subject: |
|
|
Apprentice
Joined: 23 Jan 2004
Posts: 36
|
Thanks for the reply.
Try using MQGMO_CONVERT in your get message options in your get program.
But this would again involve the broker service. Message reaches windows MQ in ASCII but with CCSID 1047 ! Is there anything WMQ offers to convert CCSID from 1047 to 437 (windows) ? Please note that windows MQ is the receiving end of channel and message HAS to be converted on windows platform. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Nov 21, 2004 12:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can write your own data conversion exit.
You should not, in general, enable channel conversion. It is far better to do the conversion at the final end point, to prevent multiple conversions from inducing character drift.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Nov 21, 2004 4:44 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You could also try and read through the CCSID setup in the manuals and if no automatic mapping exists create one.
Enjoy  |
|
| Back to top |
|
|
| sac063 |
| Posted: Sun Nov 21, 2004 5:00 pm Post subject: |
|
|
Apprentice
Joined: 23 Jan 2004
Posts: 36
|
Thanks guys.
I ran through a couple of WMQ manuals for this info with no luck. Could you also let me know which one you are refering to.
Cheers.  |
|
| Back to top |
|
|
| Nizam |
| Posted: Sun Nov 21, 2004 5:35 pm Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
I think fjb_saper is referring you to look at ccsid.tbl file which has entries for all the ccsid conversions the queue manager supports.
It is located at ROOT\ProgramFiles\IBM\WebSphere MQ\conv\table
You can search for documentation on how to edit the file in the Administration Guide.
I never used it but let us know if you have any luck with this file. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Nov 21, 2004 7:38 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Can you explain the message flow again? MF1 sends it to Windows1 which send it to MF2. Is there an app dealing with the message on Windows1, or is just a pass thru? What is the CCSID of MF1? Of MF2?
Can the app(s) that actually do something with the messages specify MQGMO_CONVERT on the MQGET?
It is rarely correct to use CONVERT_YES on a channel.
It is rarely necessary for you to have to deal with the CCSID tables internally.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kirani |
| Posted: Sun Nov 21, 2004 8:48 pm Post subject: Re: Problem with CCSID conversion |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| sac063 wrote: |
One of the point to point connection is where the broker receives the message from a mainframe-1 (CCSID 1047) without CCSID coversion and has to route the message to another mainframe-2 system (CCSID 500).
|
You can use code your message flows to do data conversion from one CCSID to another.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Nov 22, 2004 12:59 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
I think 1047 is the code page used for US English on VSE. The WMQ APR manual (table 90, WMQ z/OS CCSID conversion support) says that the conversion from 1047 -> 500 is supported on z/OS.
The best option would be to turn off conversion on the Windows->z/OS channel and do the conversion at the destination, as several other people have already said in this thread. |
|
| Back to top |
|
|
|
|
