But a Developer in my department tested IBM's MQ .NET class and is saying the following:
"But it appears the MQ Readstring() function is still returning a string that has a different asc value for the special characters that were sent in.
When I pass in a message into MQ and read it out using the MQ .NET class's, I do not get the same character that was passed into MQ. Below is an example of the hex values sent in and returned.
NOTE, this does not happen when reading the data from the API Exerciser. Just when accessing it from the MQ .NET class's.
Input: E2
ReadString() returns 47
"
One example which we hope that the APAR will resolve is:
Input to MP Queue:
<Address city="Mi‘ami" country="USA" postalCode="91100" state="CA" street1="211 Ma“in Street"/>
But Output to webpage after msg has been processed using application using MQ .NET:
<Address city="Mi?ami" country="USA" postalCode="91100" state="CA" street1="211 Ma?in Street"/>
We want the output to remain as original message.
Is there code or program to use the MQ .NET class to confirm what the developer is saying? Thanks.
Is your message format MQSTR ?
Do you use the convert option on your GET ?
Are you using the same code page CCSID on the machine doing the Get as on the machine doing the PUT ?
Is your message format MQSTR ?
Yes
Do you use the convert option on your GET ? No
Are you using the same code page CCSID on the machine doing the Get as on the machine doing the PUT ? In actual environment it is from CCSID819 to CCSID437. For the testing of CSD11's .NET class, it's on a
machine with CCSID437
Have you tried using UTF-8 instead of String ?? How would I do this? Do you have an example? Thank you
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