Quick question: How to kill a load from a file

[Mike Strout]

We are loading a relatively big file into a fileset local thread. We realized there is an unexpected legacy kill script in the route that is not reacting well with the messages being sent.

We would like to just stop the processing, remove the legacy kill script, and start over from the beginning of the file, but history tells me that Cloverleaf keeps a pointer to the last read line in the source file and the thread won’t start until that file exists in the folder Cloverleaf expects it to be in.

How do I get around this? Is there some file hidden away in the process directory or somewhere else that holds the path to the file and the line pointer?

Topic

[Mark Thompson]

Check for fileset-threadname in the process directory.

- Mark Thompson
HealthPartners

[Robert Milfajt]

If it were me, I would stop the process, move the file out of the directory and restart the process.  It’s been my experience that when you reintroduce the file to the directory that Cloverleaf starts at record #1.  Bouncing process vs. the thread, in my mind, would clear up counters, etc., and moving the file, in my option, does the same.  To be totally safe, you could rename the file something else when you put it back, but I don’t think that is necessary.

Hope this helps,

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Author]

Replies