Author |
Message
|
jefflowrey |
Posted: Thu Oct 12, 2006 12:45 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Set MQGMO_CONVERT option in your Solaris program. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
zpat |
Posted: Thu Oct 12, 2006 11:55 pm Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
The intention of MQ is that the sending application does not need to know the platform of the receiver. Sending apps should send messages in their local codepage and let the receiving apps convert it (on get).
It's called "de-coupling" and is one of the benefits of using message oriented middleware. So if the receiving application changes platform in the future, no changes to the sender is needed. |
|
Back to top |
|
 |
usakvs |
Posted: Fri Oct 13, 2006 3:29 am Post subject: |
|
|
Newbie
Joined: 04 Oct 2006 Posts: 9
|
If for any reason if we need to sedn ASCII text to solaris from Mainframe, is there any possibility of doing conversion in sending side?
The MQAPI on solaris side(part of JCAPS 5.1.1) does not support MQGMO_CONVERT option.... |
|
Back to top |
|
 |
zpat |
Posted: Fri Oct 13, 2006 3:51 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Read my previous replies. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Oct 13, 2006 6:54 am Post subject: |
|
|
Guest
|
"is there any possibility of doing conversion in sending side?
Add CONVERT(YES) to the sender channel on the sending side. This tells the sending qmgr/mca to do the conversion before the message is sent across the network.
When the sending/receiving channels attach (at channel start), they share info about their CCSIDs. |
|
Back to top |
|
 |
usakvs |
Posted: Fri Oct 13, 2006 7:54 am Post subject: |
|
|
Newbie
Joined: 04 Oct 2006 Posts: 9
|
I am not using SENDER/RECEIVER channel pair. I am using SERVERCONNECTION and I dont see option to convert the data in that. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Oct 13, 2006 4:05 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
usakvs wrote: |
Now, my question is what do I tell MF people to send ASCII format to Solaris so that I can see the same message what they send to me?
|
Mainframe systems don't send ASCII messages. They send EBCIDIC.
So the app on the MF side will produce an EBCIDIC message, it will tagged as such in the MQMD-CCSID (probably 500 or 37). The other side will do a get with convert, and MQ will convert the message from the MF code page to the code page of the receiving server. If Solaris, most likely 819, which is ASCII. Conversion betwwen platforms is one of the main benifits of MQ - use it!
For MQ's built in conversion to work, you need the MQMD_FORMAT of the message to be set to string, assuming of course the data is text data. If you got some other type of bytes in there, like a PDF or JPG, this won't work.
MQ's built in converion works on the getting side, never on the putting side. Even in the case of a SNDR channel, "putting" to the RCVR channel, its actually doing a plai old MQ convert when the SNDR MCA does a get with convert of your message from the XMITQ.
Look at the recent EBCIDIC to ASCII thread in the API Forum here. Lots more details that will help you.
zpat wrote: |
It's called "de-coupling" and is one of the benefits of using message oriented middleware. So if the receiving application changes platform in the future, no changes to the sender is needed.
|
And the other way around too! The sender can change and the receiver doesn't need to know either. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
kevinf2349 |
Posted: Fri Oct 13, 2006 4:49 pm Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
These is of course nothing to stop you writting your conversion as a part of the sending application code, but why bother if MQ is ready and willing to do this for you?
As other have said the whole idea is to let MQ does the conversion for you...autonomy is good.  |
|
Back to top |
|
 |
|