
Community Archive (Customer) asked a question.
Are there any tricks or tips to improve performance after switching from active to passive FTP with an IBMi (AS400)?
We switched from FTP (active - port 21) to FTPS (passive - port 990) using implicit encryption connection to our iSeries (AS400) and have noticed more failures of tasks and multiple tasks which do the the exact same process (just for diff named files) but react differently (#1 success, #2 failed until destination file deleted, #3 could not get to work). Are there any guidelines on what other changes need to be made when doing this?
so the tasks succeed sometimes? or they fail all the time? i think you're supposed to get a response to the " FTP SENT PASV" command, and i don't see one in the logs. are we sure the as400 is set up right for 990 and pasv? no firewalls in between? load balancers? proxy? have you tried various explicit/implicit options on the host's settings?
i found this:
https://www.ibm.com/support/pages/apar/IT23589
which is probably not your issue, but the logs there do show a response to the pasv command.
Command: PASV
Response: 227 Entering Passive Mode ......
do you have the same issues if you download [some other ftp client] and set up your as400s as 990 pasv hosts in it?
John - The issues were on uploads but after the failures I tested with the AS400 as source and destination with both directions failing at some point. The error I'm getting is "The PORT command failed." I've attached the portion of log file showing the failure. These are not new tasks or hosts. I changed the host from port 21 to implicit (secure strl/data) port 990 and the default transfer mode from Active to Passive. Also verified the tasks are using the default from host. The "overwrite duplicates" was checked prior to the change and wasn't removed
can you be more specific with the failure descriptions. is the as400 your source or your destination? when you say "tasks which do the exact same process," i'm hearing that these are newly created tasks, rather than updating the old tasks with the new hosts. so perhaps something besides the host type is different in the new tasks. moveit shouldn't care what the host type is. if "overwrite duplicates" is not checked on the destination, a task will fail to overwrite duplicates for any protocol, as in your #2 failure.