On Wed, 24 Sep 2014 07:57:21 -0400, Shmuel Metz (Seymour J.) 
<[email protected]> wrote:

>In <[email protected]>, on
>09/24/2014
>   at 01:14 AM, Paul Gilmartin
><[email protected]> said:
>
>>My source was IBM-1047; my destination was UTF-8.  But Bill Godfrey
>>had the correct explanation
>
>Curiouser and curiouser. RFC 959 does not define 557, nor does it
>require an end-of-line sequence for data in stream mode.
>

On the off chance that this is worth trying to unravel, here is an excerpt from 
Paul's post:

(begin quote)

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)

(end quote)

I was able to explain the 451 message as being related to a missing end-of-line.

Paul mistakenly thought your quoting his "Awww c'mon" comment was about the 
problem with the 451 message, but it wasn't.

The 557 message is from a different transfer, and has a different explanation, 
which is that UTF-8 translation was being attempted with SBCS.

There was a 200 warning that "some characters cannot be translated" even before 
the "get" command.

Bill

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to