Character encoding issue when posting a message to a queue that is configured on a mainframe machine

We are facing an issue with character encoding when posting a message to a queue that is configured on a mainframe machine.

Here are the details of the setup:

Sender: JMS using Websphere MQ Client API version 6

Receiver:  Mainframe server with CCSID value for queue manager set to 500 (EBCDIC)

When we send the message from sender, and retrieve it using JMS api’s, message is available in the correct format. However, if message is retrieved on the mainframe server, it has additional special characters at the beginning of the message.

If the message is sent using MQ API’s directly (bypassing JMS), and MQMessage.characterSet property is set to 500, the message is retrieved correctly without any special characters on the mainframe server.

We need to know the equivalent message property that needs to be set from JMS API’s that will have the same effect as setting MQMessage.characterSet from MQ API’s directly.

Already tried setting JMS_IBM_Character_Set to 500 on TextMessage instance but this doesn’t work.

Also, please let us know how to remove JMS specific header from the message before it is posted to the queue. We think, this is creating the problem as the message body is correctly converted.
Who is Participating?
pvashaConnect With a Mentor Author Commented:
The issue was the extra message header created by JMS which was not recognized by non JMS Clients.

The following is the solution we implemented:
We set the target client attribute on MQ Queue instance to which the message was sent. The value was set to 1 which corresponds to non JMS Client.

This solution is valid for a spring based application.

We are planning to move the app to MULE, so the JMS end points will be configured using Mule XML. Is anybody aware of setting the target client attribute in Mule Configuration XML.

Best Regards
Start by executing the following (or more conveniently and reusably ) at each end - what do you get?


Open in new window

pvashaAuthor Commented:
Please close this thread
Kevin CrossChief Technology OfficerCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.