|
Well...you could monitor the connection between their system and your system, and when it stopped, you could assume the file was there. Otherwise, there isn't a way that I know of to determine if a file has completed being transferred. I have a similiar issue with a trading partner, and ran into the same type of problem. I don't know if this solution would help, but we transfer the file (via FTP) with a .tmp extension, and then when the file is completely transferred, we rename the file to a .dat extension. That way if there are any files in a given directory with the extension of .dat, they know the file has completed being transferred. On Wed, 16 Jun 2004 13:42:51 -0700, "Bruce Barrett" <bruce.barrett@xxxxxxxxxxxx> said: > We receive this file via FTP. > > Bruce Barrett > > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of > michaelr_41@xxxxxxxxxxxxxx > Sent: Wednesday, June 16, 2004 1:32 PM > To: Midrange Systems Technical Discussion > Subject: Re: How to determine if a file transfer is complete > > How is it sent? > > On Wed, 16 Jun 2004 13:23:34 -0700, "Bruce Barrett" > <bruce.barrett@xxxxxxxxxxxx> said: > > We have one large file that is sent to us monthly, that goes to the > IFS. > > We then have an automated process to decrypt the file for internal > > processing. > > On this file only, the decryption process fails. All I have to do is > to > > move the file from an archived folder back to the original folder and > > our automated processing will decrypt the file successfully. > > We think that this is a timing issue as this is the largest file we > > receive. Our automated process runs every sixty seconds to check for > > files to process. We can not increase the time between when this > > automated job runs. All other files that we decrypt using these > > procedures process successfully the first time. > > Is there an API or a trick that we can use to verify that the file > > transfer is complete to the IFS before we try to decrypt the file? > > > > > > > > Bruce Barrett > > PMI Mortgage Insurance Co. > > 3003 Oak Road > > Walnut Creek, CA 94597 > > 925-658-6152 > > Fax 925-658-6412 > > Cell 510-520-4263 > > bruce.barrett@xxxxxxxxxxxx > > > > -- > > 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. > > > -- > > michaelr_41@xxxxxxxxxxxxxx > > -- > 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. > -- michaelr_41@xxxxxxxxxxxxxx
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.