Steve,
I don’t think this is doable in a single thread.
What you could do is route the messages to a Fileset/FTP configured Outbound thread wherein you deploy a Tcl proc to change the metadata File name wiith each message. I think there is sample code in the contrib directory and I think there has been some posted on Clovertech. If you cannot find any I think we have at least one that is rather generic.
So the receiving system would then delete each file after processing it.
However, you might want to have a copy of that file for archival purposes (what if they say they did not get some file or set of files and you need to resend?). After all FTP really is not as reliable as we might like.
In the case where you think archival makes sense, then you might want to route to an outbound Fileset-Local thread using the proc to change the file name with each message. Then have a Fileset-Local inbound thread to get each file and route static raw to a Fileset/FTP outbound thread that delivers to the receiving system (don’t forget to have a Delete Tps proc to keep the files from being delted – after all these are your archive files).
Then you would need a mechanism to manage your archive (you probably don’t want to keep those files forever). I don’t see why you could not use another Fileset-Local thread to do the archival management with Directory Parse Tps Tcl proc(s) to do the management and use advanced scheduling to meet your management timings.
Another way would be to use a Tclproc at the Outbound Tps of the Fileset-FTP (example one just two threads) and in that proc do the file I/O to write each message out to an Archive Directory before it is delivered to the receiving system.
It looks like there are a lot of different ways to do this.
The multiple thread to archive keeps everything right in front of you in the NetConfig and NetMonitor.
In my opinion File processing is a lot more complicated than real time processing.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.