| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Converting CCSID in WBIMB 5 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Savis |
 Posted: Fri Dec 19, 2003 1:55 am Post subject: Converting CCSID in WBIMB 5 |
 |
|
Novice
Joined: 19 Nov 2003
Posts: 10
|
I've got a messageflow that works in the following way:
A blob is divided into smaller chunks, the chunks then individually passes through a reset content descriptor and finally through a compute node where the packed fields get unpacked.
The blob message contains EBCDIC (CCSID 500) formatted text and packed decimal fields.
What I want in the output is a message in ASCII (CCSID 850).
When I send the message using CCSID 850 the packed decimal fields work fine but the text comes out unchanged from the input (i.e. in EBCDIC format).
When I send the message using CCSID 500 everything works fine but the output message is in CCSID 500.
Is there any ESQL code or a special node for converting between different CCSID's ? This is probably something fundamental but I just can't grasp it. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Dec 19, 2003 5:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can change the OutputRoot.Properties.CodedCharSetId before you propogate your message to the Output node.
You can specify a CCSID parameter to the CAST function, e.g CAST(InputRoot.MRM.Body.MyString CCSID 850).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Sun Dec 21, 2003 7:15 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
Internally WMQI works in Unicode.
Jeffs solution handles the cast as if the string is in ccsid 850, but in your case it is ccsid 500.
You might be changing to ccsid 850 to early, that is before the text parts are parsed, this makes WMQI to convert the text parts from 850 (instead of 500) to unicode and back to 850, with no effective change.
You should keep the original ccsid as long as possible, the very last ESQL statement for this message should be the setting of ccsid 850. Probalby you need to add an extra Compute-node for this just before the MQOutput-node.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| 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
|
|
|
|
