| Author |
Message
|
| jayZ |
 Posted: Mon Nov 14, 2016 10:44 am Post subject: Invalid Leading Characters in Messages from iSeries App |
 |
|
Acolyte
Joined: 03 Jun 2008
Posts: 71
|
I've been investigating an issue as an encoding issue for some time, but no longer believe that is the case but need help to troubleshoot. Messages from an application running on iSeries are arriving on queue with extra leading characters and I can't pinpoint exactly why.
The application connects to a v6 queue manager running locally on the iSeries and writes to a clustered queue residing on a v7.5 Linux distribution remotely. The cluster channel has 'conversion' specified and the message arrives with the correct CCSID of 1208. The iSeries queue manager is CCSID 37.
To troubleshoot, I stopped the CLUSSDR channel and looked at the message on SYSTEM.CLUSTER.TRANSMIT. That message still had the following hex 'C3A403' leading the payload of the message. I'm not sure if this was supposed be part of the MQMD or if the data is just corrupt.
Any insight on where I should check next? All other characters in the message are fine, making me think this isn't an issue with either CCSID or encoding. |
|
| Back to top |
|
 |
| tczielke |
| Posted: Mon Nov 14, 2016 12:13 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
What is the Format of the message?
0xC3A403 in 1208 converts to 0x4303 in 37. Those are not standard string bytes in 37.
What type of data is the application intending to put into the first two bytes of the payload of the message?
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| jayZ |
| Posted: Mon Nov 14, 2016 12:26 pm Post subject: |
|
|
Acolyte
Joined: 03 Jun 2008
Posts: 71
|
To your first question, the message is of type MQSTR. (I also grabbed it off the transmit queue - of course it was MQXMIT there) The first character of the file should be a string as they're trying to send data of a csv format across the queue.
I see this: ..ä."partNumber"
it should be this: "partNumber" |
|
| Back to top |
|
|
| tczielke |
| Posted: Mon Nov 14, 2016 1:08 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
It sounds then like the application started the "partNumber" text at offset 2 of the message data, instead of offset 0. Tracing can probably help confirm that, if the application team pushes back that they are not doing that in their application.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| jayZ |
| Posted: Mon Nov 14, 2016 1:24 pm Post subject: |
|
|
Acolyte
Joined: 03 Jun 2008
Posts: 71
|
| Thanks, I passed that along. Not being an iSeries guy, is that offset something build into the iSeries MQI or are you just referring to the character data passed into the message object? |
|
| Back to top |
|
|
| tczielke |
| Posted: Mon Nov 14, 2016 1:41 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
I was just referring to the character data that was PUT to the message on iSeries.
Based on the information you have provided, it sounds like the iSeries application put the following data at the beginning of the message and labeled it CCSID 37:
offset 0 = x'43'
offset 1 = x'03'
offset 2 = "p"
offset 3 = "a"
offset 4 = "r"
offset 5 = "t"
.
.
.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
|
|
