|
||||||||
|
|
#1
|
|
I've run into a timeout problem when trying to run a remote command from a
Windows 2003 server. This is NOT an activity timeout problem. There is a 60 second timeout on the QUOTE command and if the operation that is being sent to a remote server takes longer than 60 seconds to complete, the Windows ftp client is closing the ftp session and reporting that it was closed by the remote host. What I'm trying to find is some way to change the 60 seconds to a higher value. The remote host is an iSeries-400 (AS/400) and after is send files to the remote host, I run a QUOTE command that sets my program library then I send another QUOTE command that takes the first of the files I just PUT, cleans data out of the database then merges in the new data. I want to run a third QUOTE command that is similar to the second but after 60 seconds, the ftp session is closed. The command from the second QUOTE is still running on the remote host, which takes about 3 minutes total time. I'm hoping there is some kind of registry entry, or something, that will let me change the 60 seconds to something like 300 seconds, maybe more, on how long the QUOTE command is going to wait for an acknoledgement before it assumes the remote host has lost the command. I've been working on this for a week and a half and it's further complicated by the fact that I don't have access to the programs that are being run on the remote host. Thanks Bob W. |
![]() |
| Tags |
| command, ftp, timeout |
| Thread Tools | |
| Display Modes | |
|
|