View previous topic :: View next topic
|
Author |
Message |
harikiranr
New User
Joined: 08 Sep 2008 Posts: 4 Location: Chennai
|
|
|
|
Hi all,
I have a requirement where in a UTF-8 file should be ftp'ed to a windows machine. This file will be used by the third party for loading into their data base tables.
Issue:
The file received by third party is not readable.
Note: -
We are converting an ebcdic file to UTF-8 on mainframes itself.
I have used the TYPE as A and I to ftp the file.
If any one has any information, please post it. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
If the data is UTF-8 on the mainframe, and you want it in UTF-8 on the PC, you need to specify binary transfer, not ASCII. TYPE A will convert characters from EBCDIC to ASCII as the transfer proceeds, so you'll wind up with garbage data on the PC.
Depending on exactly how the environment is set up, you may need to read the Communications Server User's Guide on Use [URL] BBCode for External Links SBTRANS and SBDATACONN, as well as translate tables. But first try a binary transfer. |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
Robert, I believe that the poster mentioned that he'd tried both TYPE A and TYPE I and neither worked. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Kevin: I didn't spot that in the original ... sigh. Okay, Hari, you'll need to look up the manual and do some reading if you're insisting on transferring the file as UTF-8. |
|
Back to top |
|
|
|