| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [RESOLVED]Hex 15 |
« View previous topic :: View next topic » |
| Author |
Message
|
| lung |
 Posted: Mon Jun 18, 2012 8:25 pm Post subject: [RESOLVED]Hex 15 |
 |
|
Master
Joined: 27 Aug 2002
Posts: 291
Location: Malaysia
|
Hi,
I am having an issue with x'15' being converted to x'25'.
The message has an MQMD of CCSID 500 (EBCDIC).
All other characters are CAST properly without issue, only x'15' seems to be converting to x'25'. Even casting via RCD (to MRM) shows the 15 being converted to 25.
This is on WMB v6.
The x'15' in question is part of an account number, it is not really intended to be "New Line".
Anyone encounter similar issue before? What is the cause and workaround?
Thanks!
Last edited by lung on Tue Jun 19, 2012 1:04 am; edited 1 time in total |
|
| Back to top |
|
 |
| rekarm01 |
| Posted: Mon Jun 18, 2012 11:42 pm Post subject: Re: Hex 15 |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| lung wrote: |
| I am having an issue with x'15' being converted to x'25'. |
Please provide more details. Which component(s) is (are) performing the conversion(s)? Channel, MQInput node, WMB parser (which parser?), ESQL CAST, or something else? What is the value of the byte before and after each conversion, and what does the code look like that performs the conversion?
| lung wrote: |
| The message has an MQMD of CCSID 500 (EBCDIC). |
The MQMD (or other headers) is subject to change after each conversion. What is the value of the relevant ccsid (and Encoding and Format), before and after each conversion?
| lung wrote: |
| The x'15' in question is part of an account number, it is not really intended to be "New Line". |
If the MQMD.ccsid is 500, and the MQMD.Format indicates that the byte represents a character, then it's a "New Line". If the intent is that it should be something else, then either the Format is wrong, or the byte is corrupt.
Without more information, it's difficult to tell what the problem might be. But the WMQ InfoCenter could be useful.
| lung wrote: |
| This is on WMB v6. |
Time to upgrade? |
|
| Back to top |
|
|
| lung |
| Posted: Tue Jun 19, 2012 1:03 am Post subject: |
|
|
Master
Joined: 27 Aug 2002
Posts: 291
Location: Malaysia
|
Hi,
Thanks for the reply.
Anyway apparently the x'25' is only appearing in the trace files, when put into Q, it is still x'15'.
I guess WMB just converts the x'15' (new line) to the native CCSID's line feed (x'25) for display purposes.
So, I've been looking at a non existent issue, haha. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Tue Jun 19, 2012 1:29 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jun 19, 2012 3:57 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Is that because Broker converts ccsid-encoded bytes into UTF-16 internally ?! |
No. A UTF-16 line feed is 0x000A. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
