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
ArndW
Participant
Posts: 16318 Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:
Post
by ArndW » Tue Oct 09, 2007 12:12 am
Add a PEEK stage to your job to make sure it is the sequential write and not the Oracle Read (vs. the view-data) doing this.
ArndW
Participant
Posts: 16318 Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:
Post
by ArndW » Tue Oct 09, 2007 1:40 am
Can you add the SAP data to your peek stage as well to see if they `look' the same? That problem seems rather odd, and I don't know what could be causing it.
Maveric
Participant
Posts: 388 Joined: Tue Mar 13, 2007 1:28 am
Post
by Maveric » Tue Oct 09, 2007 2:39 am
The data coming from the Sap file when written to another sequential file is proper comes as it is in the file (Seen from the View Data tab). No change at all.
Maveric
Participant
Posts: 388 Joined: Tue Mar 13, 2007 1:28 am
Post
by Maveric » Tue Oct 09, 2007 2:41 am
The data coming from the Sap file when written to another sequential file is proper comes as it is in the file (Seen from the View Data tab). No change at all.
ArndW
Participant
Posts: 16318 Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:
Post
by ArndW » Wed Oct 10, 2007 5:46 am
If the source is the sequential file I would use a filter with a "tr" command, otherwise a CONVERT function will do the trick.
Maveric
Participant
Posts: 388 Joined: Tue Mar 13, 2007 1:28 am
Post
by Maveric » Wed Oct 10, 2007 7:40 am
Hi thanks for the replies. I have tried the following options with Convert() function using escape character.
Convert(Input.Field,CHAR(\A0\)," ") and
Convert(Input.Field,\CHAR(A0)\," ")
It is giving me a blank output. What other options can i try?
boxtoby
Premium Member
Posts: 138 Joined: Mon Mar 13, 2006 5:11 pm
Location: UK
Post
by boxtoby » Wed Oct 10, 2007 8:44 am
I've had a similar problem here.
My problem was code page related. If the code page of your source, ds job and target are not aligned you tend to get this sort of problem.
Try utf-8 as your ds job code page or nls setting and see what happens.
Hope this helps!
Bob Oxtoby
ray.wurlod
Participant
Posts: 54607 Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Post
by ray.wurlod » Wed Oct 10, 2007 4:48 pm
The Char() function requires a decimal argument. Try Char(160).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
keshav0307
Premium Member
Posts: 783 Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia
Post
by keshav0307 » Wed Oct 10, 2007 11:34 pm
you need to enable NLS, or convert the file into Windows-1252 code page,
Maveric
Participant
Posts: 388 Joined: Tue Mar 13, 2007 1:28 am
Post
by Maveric » Thu Oct 11, 2007 8:16 am
Thanks ArndW. tr command in external source stage worked. The character mentioned has the octal value of 240. The code that i used is
cat SequentialFilePath/SapArticleFileName | tr -s '\240' '^'
and latter in the transformer i trimmed the "^" character.
Thanks again for the replies.