To start, there is a difference between how certain code points are defined and how various operating systems use them.
For historical reasons, Unix misused the Line Feed (LF) character as a logical new line instead of using the more appropriate 2-character CRLF; other systems, e.g., PC-DOS used CRLF. While ASCII has no new line character, EBCDIC and Unicode each have one. Unix System Services uses NL for a logical new line, so if you binary FTP to a Unix file and tag it as EBCDIC then everything should be good to go. Does anybody know whether Unix System Services uses LF or NEL as a logical new line for files tagged as UTF-8? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Frank Swarbrick [[email protected]] Sent: Tuesday, July 27, 2021 6:01 PM To: [email protected] Subject: FTP distributed system EBCDIC encoded file We have a vendor that is providing a file that is EBCDIC (IBM-1140) encoded, but also includes an NL record/line terminator. The source system is NOT a mainframe system. I'm trying to figure out how to FTP the file to the mainframe and have it treat NL as, well, NL; i.e. a record terminator. Binary mode (no SITE options) doesn't work because it stores the NL characters. ASCII mode (no SITE options) doesn't work, I believe because it still expects the CRLF delimiter. I tried specifying "SITE TYPE E" (EBCDIC) and that also does not eliminate the NL delimiter. Any thoughts? We're seeing if the vendor can just not use a delimiter at all, but no luck yet. Note: They can create it in UTF-8, but they are including the UTF-8 Byte Order Mark (BOM). I am able to get z/OS to strip the BOM, but I have to specify the transmission as being "multi-byte", so the destination has to be VB. Which we can deal with, but we'd prefer FB as that is how we have it from the old vendor. FYI, here are the 3 "SITE" commands mentioned in the note above: encoding=mbcs mbdataconn=(ibm-1140,utf-8) UnicodeFileSystemBOM=never ---------------------------------------------------------------------- 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
