| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Client conversion from Windows to OS/390 |
« View previous topic :: View next topic » |
| Author |
Message
|
| J.Dawson |
 Posted: Thu Dec 05, 2002 9:41 am Post subject: Client conversion from Windows to OS/390 |
 |
|
Novice
Joined: 16 May 2001
Posts: 21
Location: Dallas, Texas
|
Hello,
I have a client on a Windows NT platform that is putting a message onto a remote queue defined on a OS/390 platform, which in turn sends the message to a second OS/390 platform.
The application on the second OS/390 platform does not do a 'get' with convert and thus the message is still in ascii code.
What do I need to do to convert the message to EBCIDC before the message is 'put' from the client.
Thanks,
John |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Wed Dec 11, 2002 4:21 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You can't. The NT produces ASCII messages.
What you could do is set the convert option to ON for the SENDER channel between QM1 and QM2. This attribute applies only to sender, cluster-sender, server, and cluster-receiver channels and does not apply to MQSeries for OS/390 with CICS or MQSeries for Windows.
Then any messages that go across this channel will get converted into the format needed by the recieving QM. If you have to go this route, I would make a dedicated channel just for these messages, so you are not possibly needlessly converting other messages (perhaps ones using QM2 as a hop to QMx).
The correct solution is to tell the app on QM2 to add the convert option. What is their problem anyway? 
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
