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. David -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Thursday, September 19, 2019 1:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SFTP Special Charcters On Thu, 19 Sep 2019 13:21:43 -0500, Mike Schwab wrote: >Different IBM MVS software packages used different characters sets. >APL and C files are usually the ones that require a different >translation. IBM MVS printers often used two different code pages too. > What ways are there to find which code page you're using? o UNIX "locale" command? o Terminal emulator settings? o Software package documentation? o Other (specify)? >> quote site sbdataconn=(IBM-1047,ISO8859-1) >> Possibly: quote site ENCODING MBCS quote site mbdataconn=(IBM-????,UTF-8) quote site mbdataconn=(IBM-????,IBM-1208) (or, pre-filter with iconv and transfer in binary.) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
