RoutingTransactions Reduce xtnlog file size

We are regularly running a serice that cleans out the CONFIRMED transactions in the xtn.log file, however the size of the file at the O/S level does not get reduced.

Can anyone provide me with some more info on this? Is this log file a sparse file, therefore acting like a dbf file? Does anyone have any input as to how we can “compress” this transaction log?


Has anyone found an answer to this question yet? We are running into the same problem. Any tips would be appreciated. Thanks!