You can look some table sample in TCPIP.SEZATCPX has many source tables and you can add one for you
You can use CONVXLAT to create an image to load and normally you can save it as TCPIP.STANDARD.TCPXLBIN or TCPIP.yourname.TCPXLBIN Here the JCL, You have some FTP command that load or you can put in TCPIP.FTP.DATA //ST1 EXEC PGM=CONVXLAT, // PARM='''TCPIP.SEZATCPX(US)'' ''TCPIP.US.TCPXLBIN''' //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY,BLKSIZE=80 // Giovanni System programmer -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Booher Sent: Thursday, March 05, 2015 03:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: FTP conversion Extended ASCII to EBCDIC 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? David Booher Mainframe Systems Programmer Dell | Database Management, Quest Software office +1 630-836-3196, fax +1 630-836-4099 Quest Software is now a part of Dell ---------------------------------------------------------------------- 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
