Re: Process FTP Output log

[Charles Wilt <charles.wilt@xxxxxxxxx>]

> From Scott's FTP API page...

"*After attempting to write a few programs that send files in "batch" mode,
I discovered that properly detecting errors in batch mode was not fun.*

*For my own project, I needed a way to reliably send data to a customer
every day. When this failed, or anything went wrong in the process I needed
an easy way to alert the I.S. department before the customer noticed.*
*​"*

*Don't forget to join Scott's mailing list*


*http://www.scottklement.com/mailman/listinfo/ftpapi
<http://www.scottklement.com/mailman/listinfo/ftpapi>*


*Charles*

*​*



On Mon, Jul 7, 2014 at 3:45 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

> Don't bother...
>
> Instead use Scott Klement's FTP API project to send the files.  You'll
> have much better control and feedback during the process.
> http://www.scottklement.com/ftpapi/
>
>
> Charles
>
>
>
>
>
> On Mon, Jul 7, 2014 at 3:38 PM, Gary Thompson <gthompson@xxxxxxxxxxx>
> wrote:
>
> > I am looking for a quick way to process output FTP session
> > "logs".
> >
> > We have a "never-ending" job which monitors for customer
> > deliveries which are ready and creates and sends an EDI 856
> > ASN (actually an imitation) via FTP.
> >
> > One need is to know if the FTP was successful.
> >
> > This job creates two spool files for each FTP step, one with input
> > commands and the other with output.  During the course of a day
> > there are over 200 of these files so I need to read the most recent
> > FTP output spool, which can be identified by the three parts of file:
> > Name,  Device or Queue and User Data.
> >
> > My current idea is to scan for 'bytes transferred'
> >
> > I've worked with spool API's but not here and not for some time but
> > a link to the API name and any/all hints will be much appreciated.
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.