Euro Symbol in Datastage
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 729
- Joined: Tue Apr 28, 2009 10:49 pm
Re: Euro Symbol in Datastage
Datastage Settings:
Project default (ISO_8859-1:1987)
Unix Settings:
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
Project default (ISO_8859-1:1987)
Unix Settings:
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
Karthik
-
- Premium Member
- Posts: 729
- Joined: Tue Apr 28, 2009 10:49 pm
You don't have a DataStage problem, at least not yet, so technically not something that should have been posted here.
Fix the "some code page issue" in Step 1 so your data remains intact. Perhaps the Business User will need to use a binary transfer.
Fix the "some code page issue" in Step 1 so your data remains intact. Perhaps the Business User will need to use a binary transfer.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
You will need to specify the correct code page on the mainframe FTP. Unless you can force this FTP to be in "binary" mode, then your file will have the original EBCDIC character encoding. But what is happening is that the FTP is doing an automatic code page conversion from EBCDIC to the default ASCII character set for that machine, which evidently doesn't know about the Euro symbol. Specify the correct character set in that FTP session and your mapping issues will be solved.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
I wondered about that. Seems to me the original transfer by 'the business user' to the mainframe is the one that would be doing the ASCII to EBCDIC conversion. And it sounds like the 'corruption' is happening on that initial step. From what I recall, a simple FTP script to get the file onto the UNIX server from the mainframe (step 3) won't be able to do a conversion back to ASCII so wondering exactly what utilities are involved here.
Regardless, as noted - specify the correct code page.
Regardless, as noted - specify the correct code page.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 729
- Joined: Tue Apr 28, 2009 10:49 pm
-
- Premium Member
- Posts: 729
- Joined: Tue Apr 28, 2009 10:49 pm