We received a 501 error message from a customer who was trying to connect to a Gene6 FTP Server:
The solution was to add the following “Send Command(s) after connect:
CLNT www.yourcompany.com
CLNT command: Short for CLieNT = client identification to the FTP server
If you need any help, please let us know.
Regards,
Limagito Team
Dear Users,
.. need to write an article ..
More info at rzaiqpdf.pdf
More info at FileZilla
Connecting to IBM iSeries FTP Server
Directory: /QSYS.LIB/QGPL.LIB
or
Directory: /QSYS.LIB/USERLIB.LIB
Add the following lines to the FTP setup ‘Send Command(s) after connect’ option:
quote site namefmt 1
quote site listfmt 1
quote site namefmt 1 : this command is going to tell to the remote AS400 FTP server to put himself in a regular unix standard naming schema.
quote site listfmt 1 : this command is going to tell the remote AS400 FTP server to display the list (when you do the ls command) of its file like a unix machine.
We are searching for a user who is willing to test this. Please let us know if you would like to help us.
Regards,
Limagito Team
Dear users,
A while ago we received the folllowing support question:
“I am having problem transfering a big file. The file is 959MB. We get the following error: Exception Error Control channel transfer error 114690.”
We found out that error 11469 = No data is being transferred via control channel. We asked our FTP code supplier for advice.
“Looks like a timeout-related issue. Error 114690 (SB_FTPS_ERROR_CONTROL_CHANNEL_NO_DATA) is returned if no reply was received from the control channel where it was expected to come in. According to the log, the server does not perform any activity after the file is being sent. I believe there may be a delay between the file is sent to the server and the actual response the server is sending back. This delay may originate, for example, from the server copying the uploaded file from a temporary location to its final destination. The solution is quite straightforward – instead of uploading the file as a whole, upload it in pieces. Please start with splitting the file into 100MB chunks and see how it goes.”
And that is what we did in version ‘v2018.12.27.0’. The Multipart Upload option was added in the ‘File & Directory’ tab of the FTP destination.
So what does this mean. When a source filesize is 500 MiByte or higher then this file will be uploaded in parts (chunks) of 100 MiByte. So not as a whole but in parts. Each part will be appened at the FTP server side. We use the APPE (Append) FTP command to achieve this.
A second option to achieve a multipart upload is using the COMB command (‘Use COMB’ checkbox). Important, not so many FTP servers support the COMB command (non RFC). The source file is send in segments and afterwards the FTP server will combine them when it receives the COMB command. We tested this using the trial version of Titan FTP server.
Even better is when you combine this with the Retry option. So if one of the parts would fail during the FTP upload then it will retry to upload this part again (and not the whole file).
Feedback would be much appreciated,
Happy Holidays,
Limagito Team
Limagito filemover is an automated file mover solution handling everything from moving, deleting to copying files.
Please don’t hesitate to contact us if you have any questions about our product and services.