There are two layers here. You can't say it gets converted to a backslash. More
correctly it hets translated to a code point that your emulator displays as a
backslash.
CharlesSent from a mobile; please excuse the brevity
-------- Original message --------
From: Bill Godfrey <[email protected]>
Date: 03/05/2015 3:21 PM (GMT-08:00)
To: [email protected]
Subject: Re: FTP conversion Extended ASCII to EBCDIC
On Thu, 5 Mar 2015 18:15:07 +0000, David Booher wrote:
>I have noticed when you are transferring a windows file containing a "not
>character" (x'AC') using ASCII transfer to the mainframe, it gets converted to
>"backslash" ( \ x'B7') when stored.
>
>Is there any way to get the extended Windows ASCII characters to transfer
>correctly?
I suspect that the default SBDATACONN at your site is (1047,IBM-850), which
would translate x'AC' (which is the "1/4" character in codepage 850) to x'B7'
(which is the "1/4" character in code page 1047).
If you use "quote site sbdataconn=(IBM-1047,ISO8859-1)" (if your transfer is
started from the windows end) then x'AC' will be translated to x'E0' which is
the "not character" in codepage 1047.
I don't know which codepage you have that tells you x'B7' is a backslash.
Bill
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
