Programs > CopiaFacts Server Engine Program

Tracing is controlled by checkboxes on the COPIAFACTS Options Page, Trace sub-page. The trace file written by the program is named "nodename.TRx" where x is the day number in the week (Sunday = 0). When tracing to file is enabled, a new file is started automatically at midnight, overwriting the previous week's file. When the COPIAFACTS program is started with tracing enabled, a new 'session' is added to any existing file for the day number. Normally, therefore, trace files for the preceding week are preserved in case it is necessary to refer to them for problem resolution.

The following checkboxes control the destination for tracing:

Trace to display

Displays the trace on the Summary, Trace and Scrollback pages on the COPIAFACTS console.

Trace to file

Writes the trace lines to file. File writes are normally buffered unless the Flush Trace Buffer run-time option is enabled. Copia support staff may ask you to set that option in order to capture the trace immediately before an abnormal termination. The trace file can be viewed using TRCVIEW. Using TRCVIEW on the same node as COPIAFACTS causes the trace buffer to be flushed by COPIAFACTS before loading the trace file.

The checkboxes listed below specify what is traced. If none are set, only a single trace line is written for each incoming or outbound transaction, along with any error message or debugging options output that is specified.

Trace processing states

Traces each processing state visited during the transaction. You should always set this option on when any debugging options are set, to provide a context for the debug messages. This checkbox also causes 'events' signalled by Dialogic and some other boards to be logged.

Trace hardware operations

Traces all the calls to the hardware-specific functions in the COPIAFACTS board-specific dynamic link libraries. Note that some calls will be logged even if they are not implemented for the specific board.

Trace IIF actions

You should always enable this trace while testing infobox logic, whether for custom IVR or for pre- and post-processing. It traces all $set_var variable assignments, $script texts, $set_state traps, and a number of other useful data items.

Trace outbound queue

You should enable this trace when COPIAFACTS seems not to be processing FS files which you feel are ready for transmission. It lists each pass through the FS file search operations, showing all FS files considered for processing along with the reason for selecting or not selecting each one. Do not leave this option set for more than a minute or two, because it can produce a huge amount of output. And you should usually not press the Save Settings button while this option is checked, to avoid it remaining enabled at the next restart.

Topic url: http://www.copia.com/support/refmanual/index.html?copiafactstraceoptions.htm