Long variable-length data records can cause a problem for transaction logs because they must be rolled over so fast checkpoints are not properly issued. By default, the FairCom DB Server automatically adjusts the size of the log files to accommodate long records. As a rule of thumb, if the record length exceeds about one sixth of the individual log size (2.5MB by default), the size is proportionately increased. When this occurs, the CTSTATUS.FCS file receives a message with the approximate new aggregate disk space devoted to the log files.
YES in ctsrvr.cfg disables this feature. When disabled, ensure transactions do not last longer than is necessary. If a transaction is begun and is still open when the log size is exceeded, the server will terminate.