On Thu, 5 Mar 2015 17:51:28 -0600, Bill Godfrey <[email protected]> wrote:
>On Thu, 5 Mar 2015 17:21:01 -0600, Bill Godfrey wrote: > >>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. > >Correction: to x'B0' which is the "not character" in codepage 1047. > >> >>I don't know which codepage you have that tells you x'B7' is a backslash. >> > I assumed you were using FTP, but now I see you never mentioned FTP. If your file transfer is being done by your 3270 terminal program using IND$FILE, then I don't know of any options for that method that would make it use a different translate table than the built-in one that translates x'AC' to x'B7'. Bill ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
