Well, to my understanding it is the host - the mainframe (z/OS, AS400 ?) - that performs the code page conversion from EBCDIC to ASCII. When a FTP client wants to download a file from the mainframe file system in text mode (ASCII mode), the mainframe FTP server converts the file from its native EBCDIC code page to ASCII before sending it back to the client.
My guess is that the system programmer who has set up the FTP server on your mainframe, somewhere has defined which ASCII code page to convert into.
I'm not sure about FTP server implementations on AS400 but for MVS (z/OS) this should be the case:
If you want to take control yourself of the conversions on the server from the client side issue the FTP server command:
(in this example it tells the mainframe FTP server to convert the (s)ingle(b)yte(d)ata from EBCDIC 277 (Denmark/Norway) to ASCII ISO8859-1)
Sadly you are not able to enter initializing commands in the UltraEdit FTP account manager. (It might be possible in the future - see the thread How to edit MVS files via FTP?
So your options as I see it are:
- tell your systems programmer to change the code page conversion definitions to support the ASCII code page you use on the pc
- or use a FTP client that supports initializing FTP commands.
(ps: Did you download binary (BIN) and then convert in UE using "EBCDIC to ASCII" ?)