We are using rebex.ftp.dll 4.0.4444.0 to upload small text files (actually swift messages) from a windows client to a mainframe based ftp server. TransferType = FtpTransferType.Ascii, EnabledExtensions = 0, TransferMode = Stream, Encoding = Default.
The file ends up on the mainframe side in EBCDIC as expected.
But, if we send the same file 10 times in a row with distinct filenames, some of them ends up with invalid contents on the server. really cant figure out why!
We upload them one at the time using Ftp.PutFile(localfile, remotefile)
The call succeeds, we dont get any exceptions when doing it.
I cant get access to the ftp server from my development environment, only through vpn at customer site where I have to remote desktop to, so its pretty hard to research these things. I blame it on the vpn connection, customer thinks we dont understand ftp or ebcdic, they say it worked fine in the old version, where we used darts ftp component.
dont think its related - but who does the character translation from ascii to ebcdic? if its the rebex component, then, what triggers this translation?
I cant think of anything which could disturb the transfer - anyone have a good idea?
Perhaps Transfermode = Block makes a difference on a mainframe?