Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.
Moderators: chulett , rschirm , roy
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Mon Nov 23, 2009 8:00 am
Just looks like it may be a codepage / character set issue. Can you post an example of this "binary" data?
-craig
"You can never have too many knives" -- Logan Nine Fingers
DSMaestro
Participant
Posts: 14 Joined: Thu Oct 15, 2009 6:47 am
Post
by DSMaestro » Mon Nov 23, 2009 8:17 am
chulett wrote: Just looks like it may be a codepage / character set issue. Can you post an example of this "binary" data? ...
Below is an example value for one of the binary field,
0x0000000000326839
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Mon Nov 23, 2009 8:38 am
OK, nevermind on the codepage. You've got a hex value, what are you expecting in the sequential file? That same value or do you need to... 'decode' it?
-craig
"You can never have too many knives" -- Logan Nine Fingers
DSMaestro
Participant
Posts: 14 Joined: Thu Oct 15, 2009 6:47 am
Post
by DSMaestro » Mon Nov 23, 2009 8:49 am
chulett wrote: OK, nevermind on the codepage. You've got a hex value, what are you expecting in the sequential file? That same value or do you need to... 'decode' it? ...
I'm expecting the same value in the file.
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Mon Nov 23, 2009 9:49 am
And how are you viewing the file? You'd need a hex dump to verify the contents otherwise all you'll see is what you are calling "junk values".
-craig
"You can never have too many knives" -- Logan Nine Fingers