|
Walden At 04:08 PM 11/13/97 -0500, you wrote: >Does anyone have any code they would be willing to share for checking the >success of an FTP? I have the input and output files overridden, but now I >need to actually check for a normal completion. I don't have specific code, but here's the gist of what I've done. I override stdout to a data file (not a printer file). Then, when the ftp operation is done, I read the output (log) file (RCVF) to see if the completion stuff I want is there—or warnings and errors. I think, in one case, I wrote a separate CL that did this, because of the dreaded CPF0864 problem (EOF) in CL. The ftp session has to be verbose—the default. Otherwise, the returned info is less complete. Every ftp server is a little different in the syntax of these messages. The responses for the 400 are in the TCP/IP Config & Ref manual, in the chapter on ftp server. This kind of error handling is, as you may know, very common in the Unix world, especially in shell scripts. They, to their good fortune, have grep, which does, in one command, what we have to do manually on the 400, viz., read through a file, looking for what's called a regular expression. Maybe we need a grep command, implemented with REXX, eh? Hmm, I might work on that. HTH Vernon Hamberg Systems Software Programmer Old Republic National Title Insurance Company 400 Second Avenue South Minneapolis, MN 55401 (612) 371-1111 x480 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.