[ https://issues.apache.org/jira/browse/NET-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317926#comment-17317926 ]
Sebb commented on NET-697: -------------------------- ASCII mode only works if the content is all ASCII apart from the line endings. COMP-3 values are not generally ASCII. You are going to have to find some other way to do the conversion from Windows to Z/os. > problem while transferring an Ascii file containing COMP-3 values from > Windows to Z\os > -------------------------------------------------------------------------------------- > > Key: NET-697 > URL: https://issues.apache.org/jira/browse/NET-697 > Project: Commons Net > Issue Type: Bug > Components: FTP > Reporter: Itay Itzhak > Priority: Major > > For instance, consider a file with only 1 record x’4D320A0C0D0A’ 6 bytes: “M” > + “2” + x’0A0C’ (COMP-3 x’250C’) + x’0D0A’ (indicator for end of record) > > We expect to receive only one record EBCDIC x’D4F2250C’ but instead I get two > records since x’0A’ is converted to x’25’ which is EBCDIC newline character > (LF) > > Record 1: X’D4F2’ > Record 2: x’0C’ > > In Windows, the delimiter is X’0D0A’. As a matter of fact, when I transfer > the exact same file using Windows FTP, then I get the expected result which > is a single record with EBCDIC x’D4F2250C’ -- This message was sent by Atlassian Jira (v8.3.4#803005)