On Fri, 1 Mar 2013 14:36:57 -0600, Paul Gilmartin wrote: >On Fri, 1 Mar 2013 13:15:29 -0600, John McKown wrote: > >>The translation set up with the site command is for both the PUT and GET >>commands. At the time of issuance, the ftp process does not know which you >>will do. So every IBM-1047 code point has a corresponding UTF-8 code point. >>But not every UTF-8 code point has an IBM-1047 code point. I think that is >>the meaning of the message you referenced. >> >I'm more interested in the second test case: > >>> ftp> quote site mbdataconn=(IBM-1047,UTF-8) >>> 200 SITE command was accepted > >... no warning message. Then: > >>> ftp> get foocopy >>> local: foocopy remote: foocopy >>> 229 Entering Extended Passive Mode (|||36360|) >>> 125 Sending data set /u/user/foocopy >>> 0 0.00 KiB/s >>> 557 Data contains codepoints that cannot be translated
It would have worked if you had also used this command: quote site encoding=mbcs The reason it failed the way it did is because, as you showed in your earlier post, earlier in the same ftp session you used this command: quote site sbdataconn=(IBM-1047,UTF-8) That's what causes the 557 message. The "quote site mbdataconn=(IBM-1047,UTF-8)" had no effect without also changing the encoding. Bill >>> >>> What IBM-1047 codepoint cannot be translated to UTF-8? >>> My data were: >>> >>> user@MVS:130$ od -x foocopy >>> 0000000000 B415 >>> 0000000002 >>> >And, for reference: > >user@MVS:130$ iconv -f IBM-1047 -t UTF-8 < foocopy | od -x >0000000000 C2A9 0A00 >0000000003 > >I still think it's broken. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
