RE: FTP log error checker

["Uros Davidovic" <Uros_Davidovic@xxxxxxxxxxxxxxxx>]

Dan,

depending on the system you are interfacing with, and more important, the 
FTP software itself, you will receive differing messages. One of the 
clients I worked with had responses that contained no actual standard 
response codes at all, just descriptive notification of success or 
failure, which made browsing slightly more difficult, although we did use 
RPG for this purpose.

To answer you 3-digit code question, there is a number of possibilities, 
starting with line overflow from the previous message to custom responses 
to level of logging that is set.

The best approach would be to check for as precise of a response as 
possible, also if you have access to the target system, you could test 
several standard commands that might show in your script (LS, PUT, GET, 
NAMEFMT, etc...)...

Or, you could try this thing... htpp://www.ftpplus.com
It works great...

Regards,
Uros


> 
> -----Original Message-----
> Date: Wed, 29 Jan 2003 10:41:09 -0800 (PST)
> From: Dan <dbcemid@yahoo.com>
> Subject: Re: FTP log error checker
> 
> Great article!  Looks like I'm going to search for reply codes > 299 to
> determine whether an error occurred.  This will be used to notify the
> user that "there *may* have been a problem, look at the log to verify."
> 
> Can anyone tell me whether "123 bytes transferred", where 123 is any
> 3-digit number, will ever start in position 1 of the log?  Or should I
> scan for "bytes transferred" to be on the safe side?  Are there any
> other messages that have the potential of showing a 3-digit number in
> the first 3 positions of the log?
> 
> - Dan
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>