|
I can think of a few IDEAL solutions. 1. Rename the file. Create the new one again, then get the rename file. Or, better yet, if your program that writes to the file automatically creates it if it does't exit, just rename it, get it and delete it. Easiest way if your program will recreate it. 2. Exclusively lock the file when the FTP program wants to get it. This would require a program to run somewhere that could actually lock a PC file. Lock it, get it, delete it and recreate it. 3. Have the FTP program first PUT a file to the same directory as the file you want to get. Have the program writing records to the file look for this file. If that file exists, have the writing program wait til that file disappears. 4. Use ODBC to write to an AS/400 file instead of to a Novel file. Then you don't have to use FTP at all. 5. Write a Client/Server pair to transfer records instead of ODBC. There are many, many more ways I can think of. If none of these help, let me know and I'll throw a few more out. Regards, Jim Langston Kevin Corcoran typed: > Date: Wed, 05 Jul 2000 16:46:10 GMT > From: "Kevin Corcoran" <midrange23@hotmail.com> > Subject: FTP problem > > I have a text file on a Novell Server which is constantly being added to. I > have an AS400 program queued to run every 5 minutes which will FTP from the > AS400 and GET this file. I then need to clear the server file so that the > next time I do a GET I’m only GETting new records. As there is no ftp > command for clearing a file how can achieve this? I’ve thought of DELeting > the file and then PUTting an empty version of it back on, but how do ensure > that I don’t delete any records added to it since the GET? I cannot risk > missing out on any records that would otherwise be added to the server file > while I am manipulating it. At the moment my only solution is to continually > GET all the records and then decide on the AS400 whether or not they have > already been processed, then clear the server file on a daily basis, after > production is finished. The server file will have maximum 2000 records by > the end of the day, so reprocessing the same data over and over will not > impact the AS400 too much, but it’s not an ideal solution. Does anybody know > the ‘ideal’ solution? > > TIA, > > Kevin Corcoran. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.