Hi folks We have a Unix trading partner who's sending a text file in with end of line terminators of only Line Feed (LF - x'0A' ASCII) instead of Carriage Return/Line Feed (CRLF - x'0D0A' ASCII).
As a result the line ends are not being recognised by our z/OS 1.7 FTP server and the LFs are going through as data for one line as will fit the entire length of the LRECL, and getting converted to x'25' as part of the ASCII-EBCDIC conversion. We've had similar problems before but in the other direction, with us sending CRLFs and the receiver complaining about it and insisting that WE fix it(!) which we've always done, despite me citing RFC959, by doing our own formatting and EBCDIC to ASCII translation then sending the whole lot as binary.. although I do know about the SBSENDEOL enhancements in CS 1.7. Trouble is, I can't see how I can affect anything in this case of it coming in like this; that is, unless the user gets the offending Unix version changed, which I can't see ever happening. Despite IBM's technically correct citing of RFC959, and I do tend to agree with them, in practice however their stance on it is becoming a bit of a pain when other platforms can 'accept' such transfers (although even Windows doesn't quite handle it properly). It's about to get escalated between our two companies so I need to find a resolution or workaround somehow. Has anyone experienced this also, and if so, what did you do about it? Thanks in advance Brian ----------------------------------------- Email sent from www.virginmedia.com/email Virus-checked using McAfee(R) Software and scanned for spam ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
