On Mon, 22 Sep 2014 12:01:48 -0400, Mark Jacobs wrote:
>One of my users is trying to send a mainframe file to another sever,
>converting it to UTF-8 with Byte Order Mark(BOM). So far he hasn't been
>able to get it to work, Has anyone here been able to do so? These are
>some of the things he's tried. (and variations of)
>
>site encoding=mbcs
>site mbdataconn(IBM-037,UTF-8)
>site unicodefilesystembom=always **
>
OK. There's a consensus (Shmuel and I agree) that BOM is undesirable
in UTF-8. Beyond that, I've long suspected that z/OS FTP is inadequate
in that it will not translate SBCS<-->MBCS. This really ought to be worth
an ER. An experiment with OS X client and z/OS server:
ftp> quote site encoding=sbcs
200 SITE command was accepted
ftp> quote site sbdataconn=(IBM-1047,UTF-8)
200-Some characters cannot be translated between UTF-8 and IBM-1047
200 SITE command was accepted
ftp> get chars.a2e chars.UTF-8
local: chars.UTF-8 remote: chars.a2e
229 Entering Extended Passive Mode (|||11526|)
125 Sending data set /u/user/chars.a2e
0 0.00 KiB/s
557 Data contains codepoints that cannot be translated
Awww c'mon! what codepoint can possibly have no UTF-8 representation!?
ftp> quote site encoding=mbcs
200 SITE command was accepted
ftp> quote site mbdataconn=(IBM-1047,UTF-8)
200 SITE command was accepted
ftp> get chars.a2e chars.UTF-8-M
local: chars.UTF-8-M remote: chars.a2e
229 Entering Extended Passive Mode (|||11528|)
125 Sending data set /u/user/chars.a2e
12 162.75 KiB/s
451 File transfer failed. Multi-byte data conversion error occurred
12 bytes received in 00:00 (0.30 KiB/s)
ftp> quote SYST
215 UNIX is the operating system of this server. FTP Server is running on z/OS.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
