On Thu, 19 Sep 2019 14:07:40 -0500, Mike Schwab wrote: >If the hex value seems correct, then try the target software. Your >viewing product (ISPF?) may be using a different code page. > More likely the terminal. What does your terminal (emulator) say for the host code page (readily configurable, at least with x3270.) This should match the MBDATACONN value.
I have found ISPF to be quite alert and friendly to terminal code pages, even Viewing a UTF-8 file with a Cyrillic x3270 and a UTF-8 desktop. There's an ISPF function to show the terminal code page. (I hate EBCDIC!) >On Thu, Sep 19, 2019 at 1:46 PM Statler, David wrote: >> >> In the mainframe's FTP server settings (in FTP.DATA), you can set what your >> "default" will be with the SBDATACONN (or MBDATACONN) parm. >> >> In my case I have SBDATACONN(IBM-1047,IBM-850) coded. >> >> I was trying to FTP from Windows a file that contains the character " é " to >> the mainframe. When looking at the transferred file on the mainframe, it >> looked like it was trying to use a multibyte character. >> >> Per IBM's instructions, they had me issue the following in my Windows FTP >> client: >> >> quote site encoding=mbcs >> quote site mbdataconn=(IBM-1047,UTF-8) >> >> Now looking at the mainframe file, the hex it shows looks correct (x51), but >> the displayed character is still wrong. It shows an underlined capital "J" >> character. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
