CopiaFacts logs all calls, inbound and outbound, in a transaction log. A new log file is created for every day on which any transactions occur, with a filename of either yyyymmdd.DBF or yymmdd.DBF (for example, 20011225.DBF). The log file is in dBASE format and can be analyzed using a variety of software packages. The use of 2- or 4-digit years is controlled by the COPIAFACTS program run-time option 2-Digit Year DBF Name. The default is 4.

Each document or image requested results in a separate log transaction. The transaction includes the image number, the call number, the date and time of the call, the number of pages sent, the transmission status, and the fax CSID (answerback) of the caller. You can also save custom data in the log file by assigning values during the call to system variables DATAx. See Appendix E: Transaction Log File for details of the file layout.

When logging transactions COPIAFACTS will attempt to lock the file before appending the new transaction. It will try to do so a maximum of 5 times. If the lock attempt fails, the transaction will not be recorded and COPIAFACTS will continue with the next transaction and/or call. The failed lock attempt will be counted as a lock error and will appear in the summary section of the COPIAFACTS status screen. You can change the number of lock attempts using $lock_tries or set the size of the log buffer to a higher value with $log_queue.

The DBF log file is protected by a .LCK file of the same path and filename. This is a precaution to prevent accidental re-creation of the file, or creation attempts by more than one node. Otherwise, a momentary network glitch could make one node think that the DBF was absent, and the creation of a new one could wipe out a whole day's log if it then happened to succeed as the network came back up. If there is a need to recreate a .DBF log file (for example if it has been accidentally deleted), you should manually delete the .LCK file and CopiaFacts will then recreate the DBF log.