| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Conversion Issues from Sol. to AS400 |
« View previous topic :: View next topic » |
| Author |
Message
|
| martc |
 Posted: Wed Mar 23, 2005 3:53 pm Post subject: Conversion Issues from Sol. to AS400 |
 |
|
Apprentice
Joined: 23 Mar 2005
Posts: 39
|
Hi;
The problem I'm having is when data is sent from our WBI brokers on Solaris to the As400, we are automatically seeing a CCSID conversion. To test this, I shut the channel down and viewd the msg in the xmit q. There it had a CCSID of 437. With no CONVERSION on either MCA and no channel EXITS's etc it was 37 in the AS400.
The problem were having is when we do a MQGET using MQC.MQGMO_CONVERT the data is all garbled but when we dont use this gmo option it looks fine. So there appears to be a double-cnversion.
Question: Why is there (it appears) an automatic conversion between the two MCA'a and Secondly, if the CCSID at the time of the GET is already its native CCSID should the MQC.MQGMO_CONVERT make a difference.
Anybody's insight into this would be much appreciated. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Wed Mar 23, 2005 5:40 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You have the convert option turned on on the channel. Turn it off. This is far from the preferred way of handling conversion.
The getting app on the AS400 should be doing a get with convert.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| martc |
| Posted: Thu Mar 24, 2005 9:41 am Post subject: |
|
|
Apprentice
Joined: 23 Mar 2005
Posts: 39
|
Peter, I really dont. The Data Convert Option on the sender channel is OFF and no channel EXIT on the reciever.
I agree, the receiving app should be doing the CONVERT but when we do the data comes in garbled.
Other ideas?
1 : dis channel (SACSUN7.TOR530d01)
AMQ8414: Display Channel details.
CHANNEL(SACSUN7.TOR530D01) CHLTYPE(SDR)
TRPTYPE(TCP) DESCR(Sender channel to Adapter)
XMITQ(TOR530D01) MCANAME( )
MODENAME( ) TPNAME( )
BATCHSZ(50) DISCINT(6000)
SHORTRTY(10) SHORTTMR(60)
LONGRTY(999999999) LONGTMR(1200)
SCYEXIT( ) SEQWRAP(999999999)
MAXMSGL(4194304) CONVERT(NO)
SCYDATA( ) USERID( )
PASSWORD( ) MCATYPE(PROCESS)
CONNAME(TOR400(1415)) HBINT(300)
BATCHINT(0) NPMSPEED(FAST)
SSLCIPH( ) BATCHHB(0)
LOCLADDR( ) KAINT(AUTO)
MCAUSER( ) ALTDATE(2005-01-19)
ALTTIME(11.28.17) SSLPEER()
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( ) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 24, 2005 2:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The data might really get sent in ccsid 37
This depends on the setup of the messages and jndi.
You can entice a qmgr to put all msgs on a queue in a specific ccsid. (see one of my previous posts)
You might not see that right away as the xmitq header might obfuscate this.
Enjoy  |
|
| 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
|
|
|
|
