On Tue, 23 Sep 2014 09:23:54 -0500, Bill Godfrey <[email protected]> wrote:
>
>>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.
>>
>I have seen the very misleading 451 message when attempting this with a USS
>file in which the last line does not end with hex 15.
>
>If that is the case with your chars.a2e file, if you try the multi-byte
>transfer again after appending hex 15 to it, it should work.
>
Yup. Works. Given that the TCP/IP message texts are implementation-defined
they could supply in this case a more meaniingful message text, such as:
451 Incomplete last line
Remote system type is MVS.
ftp> ascii
200 Representation type is Ascii NonPrint
ftp> quote site encoding=mbcs
200 SITE command was accepted
ftp> site mbdataconn=(IBM-1047,UTF-8)
200 SITE command was accepted
ftp> get chars.a2enl
local: chars.a2enl remote: chars.a2enl
229 Entering Extended Passive Mode (|||11776|)
125 Sending data set chars.a2enl
387 560.72 KiB/s
250 Transfer completed successfully.
387 bytes received in 00:00 (1.46 KiB/s)
501 $ cat chars.a2enl
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ
Thanks,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
