| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Convering an Ascii data to ebcidic |
« View previous topic :: View next topic » |
| Author |
Message
|
| yshakraj |
 Posted: Sun Aug 05, 2012 6:35 am Post subject: Convering an Ascii data to ebcidic |
 |
|
Voyager
Joined: 14 Sep 2011
Posts: 91
|
How to convert an ascii data to ebcidic data through esql?I'm reckoning upon converting to ebcidic using CAST function. any encoding is needed?could please help me  |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun Aug 05, 2012 6:53 am Post subject: Re: Convering an Ascii data to ebcidic |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yshakraj wrote: |
| How to convert an ascii data to ebcidic data through esql? |
Let WMB do it.
| yshakraj wrote: |
| I'm reckoning upon converting to ebcidic using CAST function. |
How are you reckoning that? WMB understands EBCDIC data & can either read it or write it out for you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Aug 05, 2012 8:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
ENCODING only applies to numeric values.
Does your 'ascii' data contain numeric values that must be treated as numeric values in order to be properly converted?
How do you know one way or another?
CCSID or CodedCharSetID or Coded Character Set Identification - as you choose, so long as you understand what it means - applies only to character data.
Does your 'ascii' data contain character values that must be treated as character values in order to be properly converted?
How do you know one way or another?
There are several options available to convert data using WMB. One way is to make sure that the logical data is correctly in a known combination of CCSID and Encoding and then tell Broker that the output data should be turned into a different CCSID and Encoding when it serializes the logical message tree into an output bitstream, or similarly allow Broker to parse the input bitstream into a logical message tree (this automatically converts the data into Unicode).
Another way is to use CREATE FIELD PARSE() or ASBITSTREAM to do this same process.
Another way, as you appear to have chosen, is to CAST to a BLOB and then CAST to a CHAR, specifying the appropriate destination and source CCSIDs.
What process did you follow to evaluate these choices and then determine the method you will use?
How do you know that your choice is the correct one for your situation? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Aug 06, 2012 5:05 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| zpat |
| Posted: Mon Aug 06, 2012 5:09 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| lancelotlinc wrote: |
| When you attended the WM663 class, what did your instructor say about it? |
I think you know the answer to that one...  |
|
| 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
|
|
|
|
