RE: FTP actual delivery confirmation -- MIDRANGE-L

I didn't think this was true, so I tested it. Turns out we were both wrong. Any file transfer over 99999 bytes will have the first three characters in the log as numeric digits. It gives the number six spaces, and once it extends past that is starts shifting over.

Here is an example:

put calendar
227 Entering Passive Mode
150 Sending file to member
226 File transfer complete
86016 bytes transferred i
put evfevent
Member EVFEVENT in file EV
put mcpbcls
227 Entering Passive Mode
150 Sending file to member
226 File transfer complete
11347362 bytes transferred

So for the first transfer the number of bytes transferred was less than 6 digits so you have a space in front, but for the second transfer, there are more than six digits so the first three characters of the line are numeric. However this means that you could look for three digits and a space and you would then be safe.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx

-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: "Morgan, Paul"
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 11/07/2011 01:41PM
Subject: RE: FTP actual delivery confirmation

Mark,

The actual message put in the log for bytes transferred is spaced over a couple of blanks so this won't happen. Any 226 or 530 in the first three characters of the line is an error message.

Paul Morgan

Principal Programmer Analyst
IT Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: Monday, November 07, 2011 1:16 PM
To: Midrange Systems Technical Discussion
Subject: RE: FTP actual delivery confirmation

This could work if you don't have a 226 or 530 byte file. At that point your log scanner might confuse the XXX bytes transferred message with a status message.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx

-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Kurt Anderson
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 11/02/2011 02:38PM
Subject: RE: FTP actual delivery confirmation

Thanks Dennis.
I've modified and tested our FTP service program to look for '226 ' instead. Also modified our login check to look for '530 '. Hoping it's enough to check starting in the 1st position and that the ftp code would always have a space following it.
http://en.wikipedia.org/wiki/List_of_FTP_server_return_codes

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis
Sent: Wednesday, November 02, 2011 12:55 PM
To: Midrange Systems Technical Discussion
Subject: RE: FTP actual delivery confirmation

The common factor here . . . which _is_ standardized, is the 226 numeric return code. In fact, as a part of that same standard, any 2xx numeric return code indicates lack of terminal error.
++
Dennis
++
"Always live within your income, even if you have to borrow money to do so."
-- Josh Billings

Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++

"Alan Shore" <ashore@xxxxxxxx> wrote:

Hi Kurt
Unfortunately not all ftp software/systems return the same values For
example, here is what we have for Transfer complete
226 File transfer completed successfully.
226 File transfer complete.
226 Transfer complete.
226 Transfer Complete
226 File receive OK.
226 File received ok
226 transfer complete
226 Transfer completed.
226 Transfer completed successfully

Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Wednesday, November 02, 2011 1:08 PM
To: Midrange Systems Technical Discussion
Subject: RE: FTP actual delivery confirmation

Excellent, I'm going to have to review Scott's API. However I recently
wrote a FTP Scripting service program. It currently uses SQL to check
the output for:

D FTP_STS_HOST1 S 13a Inz( 'Unknown host%' )
D FTP_STS_HOST2 S 17a Inz( 'Cannot find host%' )
D FTP_STS_LOGIN S 32a Inz( '530 Login or Password +
D incorrect.' )
D FTP_STS_OK1 C '226 File received ok.'
D FTP_STS_OK2 C '226 Transfer complete.'
D STS_BADLOGIN C 'Failed to Login: '
D STS_BADSERVER C 'Failed to Connect to Server: '

-Kurt

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, November 02, 2011 10:01 AM
To: Midrange Systems Technical Discussion
Subject: Re: FTP actual delivery confirmation

I've not used it, but does this tell you what confirmation messages may
be received?
http://www.scottklement.com/ftpapi/

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: jmoreno@xxxxxxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx,
Date: 11/02/2011 10:10 AM
Subject: FTP actual delivery confirmation
Sent by: midrange-l-bounces@xxxxxxxxxxxx

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.

--
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.