Re: FTP log error checker

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

REXX would be an excellent tool for parsing this output. You can tokenize 
the record, blanks are dropped in the process. REXX was written with 
text-processing in mind - it's really very powerful and easy, too.

Regards

Vern

At 07:28 AM 1/29/2003 -0800, you wrote:
> Guess I should have checked the Midrange-L inbox this morning as well
> as the archives.  I saw the reference to
> http://www.the-eggman.com/seminars/ftp_error_codes.html.  For those who
> prefer a more "official" list, see
> http://publib.boulder.ibm.com/pubs/html/as400/v4r5/ic2924/index.htm?info/RZAIQFTPSRPLY.HTM
> (Yes, it's InfoCenter, I actually found something useful on the first
> search I submitted!  Wow!  Bookmanager / Softcopy still rules, tho <g>)
>
> The "TCP/IP Configuration and Reference" (Softcopy!) mentions:
>   Three-digit FTP error reply codes start with 4 or 5. Be
>   careful to avoid messages such as '467 bytes transferred...'.
> But it appears that all the 'nnn bytes transferred" messages always
> leave position 1 blank, so my assumption is that checking for 3 digits
> in positions 1-3, followed by a blank in position 4 should *guarantee*
> that it is an FTP result code of some sort.
>
> THE BIG QUESTION:
> Is it safe to use logic that says everything worked great as long as
> there are no 3-digit codes greater than 299?
>
> - Dan