Output to multiple files

You will need a Tcl proc to do that.

I have one – if you want it email me.

I thought you wanted to place one message per file using fileset protocol.

That is the proc I was offering not a filter proc.

I use a TCL proc called tps_fileset_outbound to write one message per file.

Here is a URL with Source code and screen shots to illustrate:

It would go in the Outbound TPS.

The way that I have handled this in the past is to have the third party pick up files like *.rdy .  Cloverleaf puts in files to the dir without the extension.  I then have a script that looks at the dir every minute and renames files that are over three minutes old.

A bettor way IMHO

Write the files out to a temp directory.  Then have another thread in the same process with UPoC protocol.  Schedule that thread to run as often as you want to move files.

When the UPoC thread runs, move (don’t copy) the files to the final directory.  Move is an atomic operation so no way the fles can be picked up early. Also, since the UPoC thread runs in the same process there is no way the engine can be writing files at the same time you perform the move.

I posted how we’ve been batching up real-time numfiles for FTP on a scheduled basis on the second page of this URL:

    <a href="http://clovertech.infor.com/viewtopic.php?t=1907&postdays=0&postorder=asc&highlight=batchnumfile&start=15&#8243; class=”bbcode_url”>http://clovertech.infor.com/viewtopic.php?t=1907&postdays=0&postorder=asc&highlight=batchnumfile&start=15

The basic concept at a high level is that we have a real-time interface create a num file of each ADT message real-time so that each num file has one ADT message in it.

Since the num files are sequntially named, when the directory listing is sorted they are also in chronological order.

A proc called batch_num_file.tcl that is argument driven is run on the desired time interval via a cron entry to batch up the currently available num files into a concatenated batch file, which is then available for the destination system to FTP/get or have Cloverleaf FTP/put.

In our case, I prefer to have the source system FTP/get the file which happens once an hour for this interface.

Granted much of the solution uses standalone scripts to complement cloverleaf because at that time in the year 2000 I was not fully capable in cloverleaf.

It has wokred well so no motivation to change it plus it hasn’t ever been impacted by a cloverleaf upgrade.