Hello Tim, all @ 3000-l,

------------------------------------------------------------
>> James, I think your example says it all.  You missed the
>> point of this thread. Exitonerror means it should not
>> process any more ftp commands after an error occurs, it
>> should just set the VARs accordingly and abort.  The QUIT
>> command (nor any other command) should never have been
>> processed.
------------------------------------------------------------

Sorry, I disagree and the GET example provided is an excellent sample of why.

First to avoid any confusion... the "exitonerror" is internally calling "quit" which is not related to a "QUIT" command which may or may not be in the FTP job or stdin script.

The importance of internally calling "quit" on an "exitonerror" condition is it drives an orderly shutdown of the FTP Client/Server connection.  The reason to do this is if we do not perform an orderly shutdown of the FTP Client/Server connection, then in some cases the remote FTP Server will get stuck (hung waiting for a command), or will bark an error message due to an error termination.  As you may guess, this is not an appropriate response in our example where the "exitonerror" condition is triggered due to a missing file on the remote host which may be a possible "expected" condition or outcome.

The solution to our problem here is to make sure that we preserve the correct variable settings when we call quit from "exitonerror".

I hope this helps.




Regards,

James Hofmeister
Email: <first>.<last>@hp.com
Hewlett Packard - Global Solutions Engineering (WTEC)
P.S. My Ideals are my own, not necessarily my employers.

---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *