FTP without file deletion

Place hcitpsmsgkill in the deletion tps

Michael,

I don’t think that will do the trick because there is no message at that point only the name of the file that will be deleted as each file is finished being read.

I should have been more concise.

In order to accomplish:

However, I want the file to remain on the server.  I do not want CL to delete it.

Place hcitpsmsgkill in the deletion tps

Still won’t work Mike.

Put in a deletion proc that always returns an empty list.

This proc is similar to the directory parse proc.  It gives you a list of files it proposes to delete and you return a list you want it to delete. The main difference here is you are provided the complete path.

I guess my question is if you don’t delete it what will keep you from processing it over and over?

Not to beat a dead horse, but…

I am on 5.4.1 AIX

My understanding and past use has been that this still is a point of control that gives you a message handle to a message that contains a list of files it proposes to delete. Similiar to what you said.

If we return a KILL disposition, no list goes through and therefore,

nothing to delete.

What am I missing? Is this something that has changed with the introduction of tclcurl in 5.5+ versions? Or have I been smoking something other than cigarettes while working?

Nothing has ever changed with Fiieset Delete.  It works the way it always has.

Here is a simple delete proc.  Set up a test Fileset/Local or FTP thread and put it in there then look at the log file.

Also note, as I said you will process the same file over and over.

The purpose of this, for Fileset/Local only would be to give you the opportunity to archive the files rather than delete them.  FOr FTP you don’t have the access

If you do not remove the file from the  directory and it has the same name the engine will process it over and over.

If it only processes the file with current date and it only runs once per day, it should be OK since each time it runs it is looking for a different file name

If it were me, to be sure, I would set a non-volitle flag somewhere to indicate I had already processed the file.  

For example, you could simply write a zero-length file of the same name in a local directory.  Then before you tell the engine to fetch that file check to see if it exists on the local directory,  If not fetch.  If so, ignore.  Also, when checking the local file, delete any older than today to keep them from accumulating.

There are other methods, of course

Use a proc similar to the one I posted and have it return the empty list and it will not delete