Problem

The cft.out file contains all output of CFTUTIL when called from post-processing procedures.
It makes that file growing quite fast when the monitor have to manage a heavy load of transfers.

You can avoid CFTUTIL program to log output messages, it will reduce in a significantly way the number of lines recorded in the cft.out file.

Just add the option "/m=40" to all CFTUTIL call in post processing scripts:
For example:
Use cftutil /m=40 send part=part1,idf=test instead of: cftutil send part=part1,idf=test

All CFTUxxx messages will be filtered.

Note:
The messages filter argument works for all UNIX and Windows CFTs:

I.E:
Send command issued on a CFT for Windows without the messages filter option:

C:\Axway\Synchrony\Transfer_CFT\runtime>cftutil send part=part1,idf=test
CFTU20I
CFTU20I CFT Windows NT
CFTU20I Version 2.7.1 20110523
CFTU20I (C) Copyright AXWAY 1989-2007
CFTU20I ====> Starting Session on 26/07/2011 Time is 10:28:32
CFTU20I Parameters file :C:\Axway\Synchrony\Trans..FT\runtime\\data\cftparm
CFTU20I Partners file :C:\Axway\Synchrony\Trans..FT\runtime\\data\cftpart
CFTU20I Catalog file :C:\Axway\Synchrony\Trans..FT\runtime\\data\cftcata
CFTU20I
CFTU00I SEND _ Correct (part=part1,idf=test)
CFTU20I Communication file row number used: 00000049 on 20110726 Time 10283230
CFTU20I Number of Command(s) 1
CFTU20I Number of error(s) 0
CFTU20I Ending Session on 26/07/2011 Time is 10:28:32
CFTU20I Session active for 0:00:00

Same SEND command issued with the optional messages filter argument

C:\Axway\Synchrony\Transfer_CFT\runtime>cftutil /m=40 send part=part1,idf=test
C:\Axway\Synchrony\Transfer_CFT\runtime>