| Author |
Message
|
| kvkirankumar |
 Posted: Wed Jun 03, 2015 1:43 am Post subject: Unreadable Response from MQs v7.5 |
 |
|
Newbie
Joined: 03 Jun 2015
Posts: 2
|
Hi,
I need help in using IBM MQueues with 7.5 version. We work on Pega Tool (Java Platform) using Connect-MQ rule to pass Request message to a Mainframe System via IBM MQ v6 Request Queue . Mainframe system process this message and repond with another message to Pega using IBM MQ v6 Response Queue.
Now, recently these MQs are upgraded to 7.5 version. After upgradation completed, when we are testing an MQ transaction, we are receiving the response in unreadable format like below.
<Response>4Vx ÉÕåÁÓÉÄ@ÙÅØäÅâã</Response>
When we further analyzed, we identified that this is issue with Character Set Conversion. Mainframe system uses EBCDIC Character Set. As Pega resides on Unix, it uses ANSI Character set. Usually, the Response MQ converts the "Response Message" into Calling App's Character Set (i.e., ANSI Character set). Apart from this, we have the option to apply MQC.MQGMO_CONVERT constant to convert data from one Character Set to another.
We tried all these possible options, but still we are receiving the same unreadable format response. Any suggestions to resolve this issue?
Code Snippet:
resMsgOpt.options = com.ibm.mq.MQC.MQGMO_WAIT | com.ibm.mq.MQC.MQGMO_CONVERT; |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jun 03, 2015 2:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What is the format of the message? (MQFMT_????)? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 03, 2015 5:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Have you confirmed that the data in the mainframe is not in the right CCSID for the XML document you are processing?
If the wrong ccsid is used to insert a specific field into *part* of a document, MQGMO_Convert will not help. It only converts the *whole* document. If part of the document is in a different CCSID, it will treat that part as being in the CCSID of the message, not in the CCSID of that part of the data.
That is, your XML document is broken. |
|
| Back to top |
|
|
| kvkirankumar |
| Posted: Wed Jun 03, 2015 7:18 am Post subject: |
|
|
Newbie
Joined: 03 Jun 2015
Posts: 2
|
| I am using MQSTR format. Does this need to be changed ? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 03, 2015 7:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| kvkirankumar wrote: |
| I am using MQSTR format. Does this need to be changed ? |
The data inside the message needs to be changed. |
|
| Back to top |
|
|
| tczielke |
| Posted: Wed Jun 03, 2015 7:37 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 03, 2015 8:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| tczielke wrote: |
| Running and reviewing a trace (i.e. strmqtrc) would be helpful here to understand what is happening with your message conversion |
I think it would show that all of the conversion was performed successfully.
The input message is broken. Full stop. |
|
| Back to top |
|
|
|
|
