| Author |
Message
|
| Henry |
 Posted: Fri Apr 30, 2004 1:06 am Post subject: data conversion on CAF |
 |
|
Acolyte
Joined: 08 Oct 2003
Posts: 73
|
When I put msg from a MQ client on windows platform to 390 platform, the msg can't be read on 390 platform. From the msg, I can see that the encoding number and the CCSID are different.
for example, environment
client: Windows 2000
Queue manager: OS390
msg is put from client onto the queue manager via CAF.
The encoding number is 546 and the CCSID is 437
However, the msg is put from OS390 itself
the encoding number is 785 and the CCSID is 500.
this is related to the data conversion, I think. How can I put the msg from Windows platform to queue manager on OS390 read?
Do I need to put any exit on the client channel? |
|
| Back to top |
|
 |
| offshore |
| Posted: Fri Apr 30, 2004 3:19 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
Henry,
I have to plead ignorance on how to answer you question using a client channel.
I personally wouldn't recommend converting the message via channel.
Let the OS/390 MVS application do a convert upon getting the message off the queue. The applications people can specify an MQGMO_CONVERT the program.
If you (as the admin) are needing to read a message on a queue there IMHO there are better ways to go about accomplishing that task. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Apr 30, 2004 4:49 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Clients always put in the CCSID of the machine that the client is on, not the server that actually holds the queue.
You can override this at MQPUT time, or by setting an Environment variable on the MQCLient machine, MQCCSID. There is also a section on this in Chapter 11 of the MQClient manual.
But, I agree with offshore. Don't interfere with the basic design. Do the MQGET with convert on the mainframe side and let the WIn MQ client do its thing normally.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Henry |
| Posted: Wed May 05, 2004 1:56 am Post subject: |
|
|
Acolyte
Joined: 08 Oct 2003
Posts: 73
|
I agree both of you that didn't do any conversion on client side.
I had put msg from solaris client or windows client onto the OS390 Q manager. When I browsed the msg from the admin console via the browse function, the msg cannot be read in which it is in ACSII. However, I can get it through the programme.
when any msg put onto the OS390 itself, the client on solaris and windows can't get the msg with reason code 2119. it is about MQRC_NOT_CONVERTED. When I use the GMO_CONVERT from the client programme. The error 2195 is thrown.
How can I get the msg back from the client? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed May 05, 2004 1:34 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Is the MQMD_FORMAT of the message MQSTR? It needs to be in order for standard MQ convert to work.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Henry |
| Posted: Wed May 05, 2004 5:38 pm Post subject: |
|
|
Acolyte
Joined: 08 Oct 2003
Posts: 73
|
| Yes, the MQMD_FORMAT of the msg is MQSTR. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 06, 2004 7:06 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Huh. Should work then.
Once the message is on the queue on the mainframe, go to a command prompt on a Windows machine where MQ client is installed. Issue a SET MQSERVER to get your dos window pointing at the mainframe QM, and then use amqsbsgc to browse the message. What does that return?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Henry |
| Posted: Thu May 06, 2004 10:09 pm Post subject: |
|
|
Acolyte
Joined: 08 Oct 2003
Posts: 73
|
| the problem is solved. thanks for all your help!! |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri May 07, 2004 9:26 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Henry, and anyonbe else how posts a "Solved" message,
Just a thought. It would be nice if you posted what you did to solve this, not just that it's fixed. That way anyone else with a similar problem, who searches the forum (yeah, right  ) might be able to fix their problem with having to ask again.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
