Keep the NLs and write a quick and dirty to post-process, splitting the records? CharlesSent from a mobile; please excuse the brevity. -------- Original message --------From: Frank Swarbrick <[email protected]> Date: 7/27/21 6:01 PM (GMT-05:00) 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=mbcsmbdataconn=(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
