cancel
Showing results for 
Search instead for 
Did you mean: 

MQ JMS non-compliant header field in HEXADECIMAL

mayur_patel6
Participant
0 Kudos

Hello Experts,

Our scenario include a sender MQ Channel and a Receiver File adapter. We are passing a flat file using an Integrated Scenario to the file adapter. We are using the JMS CorrelationID header field to pass the file name to the file adapter. Unfortuantely, File adapter is receiving the filename in a HEX. So, the Filie adapter is writing the filename as huge value. I am not sure how this JMSCorrelationID header field is converting a string into a HEX value.

Any kind of help would be appreciated.

Thanks,

Mayur

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member206760
Active Contributor
0 Kudos

hi

Try using 2 ways..

1. As Koen said.tick the JMS coorelation id on the adapter specific message attributes on the sender JMS adatper...

Then in a UDF....access this field and convert its byte format to string...but there might be character set issues

2. in the co-relation setting , set the PI message ID - to JMS correlation ID and tick the remove ID marker.

With this JMS corelation ID will be passed to PI message ID and then in UDF extract the PI message ID and pass it to filename

Edited by: Tarang Shah on Mar 25, 2010 1:52 PM

Former Member
0 Kudos

Mayur,

The JMS Correlation ID is a 24 byte field, not a character field. Please see this thread on MQSeries.net: http://mqseries.net/phpBB2/viewtopic.php?p=83246&sid=d52620373533995d245399da7f4db885

Regards,

Koen