|
Jeff,
Thanks, I needed that!
Totally over-looked OVRDBF.
I have a copy of FTPAPI and want to implement but I'm
in results NOW mode - and you just saved my life!
And thanks also to Charles - I believe I am on Scott's mailing list
so I'm hoping to circle back because we too need reliability which
my current hack will not address.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jeff Young
Sent: Monday, July 07, 2014 1:43 PM
To: Midrange Systems Technical Discussion
Subject: Re: Process FTP Output log
Gary,
Others here will suggest that you use Scott Kelments' FTPAPI utility that
will give you finer control and total error handling.
If you want to process the FTP Output Log, I would suggest that you create
a Source File and prior to the FTP command issue an OVRDBF command as
follows:
OVRDBF FILE(OUTPUT) TOFILE(your file) TOMBR(your member).
The file name OUTPUT is used by FTP to write the output log.
Jeff Young
Sr. Programmer Analyst
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.
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.
--
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.
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.