Re: FTP actual delivery confirmation

[Aaron Abreu <abreual@xxxxxxxxxxxxx>]

I have put all my repetetive FTP's in CL's

That way I can redirect (override print file) all the FTP session messages
to
a source file set up with members named after each FTP job.
This retains the messages until I run the job again, or in some cases,
I do not clear the message file but continue to write to it so I have
an FTP  "history".

I have another job that runs and scans all the message text
members and list out any KEY WORDS,  such as "unsuccessful", "error"
or any other message words I need to know.

Thats as close to "notification" as I can get in our shop.

It works well and gives me a quick list of all the 40 something
FTP's that run at night so I don't have to look at each message file
seperately.
Examples can be provided if you are interested.
Aaron







On Wed, Nov 2, 2011 at 9:06 AM, <jmoreno@xxxxxxxxxxxxxxxx> wrote:

> Hello group,
>
> Is it possible to get an actual delivery confirmation of an FTP function
> after I have delivered IFS files to a remote location?
> Can this be achieved in a single command stream?
>
> We had an incident were the remote location effectively responded the PING
> but the documents were lost.
> At the moment our Batch FTP outbound process only checks for an abnormal
> error of the plain FTP command.
>
> Would it be sufficient and reliable to inspect the verbose of the FTP
> Output?
>
> Just wondering and looking for your assistance.
>
> Thanks in advance for your answers and recommendations
>
>
>
> Jorge Moreno
> Military Car Sales, Inc
> Woodbury, New York
>
> This email, including its attachments, may contain information that is
> confidential and may be protected by federal and/or state laws and
> regulations, or other confidentiality privileges. This email, including
> its attachments, may contain non-public information, therefore it is
> intended to be conveyed only to the designated recipient(s). If you are
> not an intended recipient, please delete this email, including its
> attachments, and notify the sender. The unauthorized use, dissemination,
> distribution or reproduction of this email, including its attachments, is
> prohibited and may be unlawful.
> --
> 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.