Function Keys
The list of trace options and corresponding function keys is as follows:
| F1 | select summary screen |
| F2 | select trace screen |
| F3 | select scrollback screen |
| F4 | Trace to display |
| F5 | Trace to file |
| F6 | Function entry/exit tracing |
| F7 | Thread start/stop tracing |
| F8 | IIF action tracing |
| F9 | Processing State tracing |
| F10 | Hardware Operations tracing |
| F11 | Temporary debugging messages |
| F12 | Outbound queue search tracing |
If you press the 'd' key (lower case D), a window will be displayed showing the load addresses of all the Copia and system DLLs in use by the COPIAFACTS program. You may be asked to do this by Copia support staff if problems are detected in one of the loaded DLLs. If the display is blank, this will usually be because PSAPI.DLL is not in your SYSTEM32 folder.
The 'l' key (lower case L) displays a summary of system license information in the trace file or trace display.
The 'r' key (lower case R) places a snapshot of the CPU utilization of each thread in the registry at HKCU/Software/Copia/CPU_Limit. This is intended to assist Copia support staff in debugging thread issues. If you use the 't' key (lower case T), the snapshot is also written to FFTRACE, if running with COPIAFACTS selected under File/Applications. The registry is used to save the information in case the problem being investigated prevents trace file writing. A snapshot made in the previous 30 minutes will be shown at the end of the system information trace on COPIAFACTS restart, and can also be viewed using CFINFO. A snapshot is also made automatically if the CPU Limit is exceeded.
Pressing Control-H displays a count of the Windows handles in use by the process, and how it has changed since the program completed initialization.
The 's' key (lower case S) (when the Summary or Trace tab is active) opens a window showing statistics about the scanning of the TOSEND folders. This information can be used to tune the scheduling of TOSEND queue priorities, and in a multiple-node system may help to schedule work between different nodes. [Note that upper-case S starts a controlled shutdown]
You can select bar-charts of three types:
•An analysis of the time spent scanning in each folder, in seconds
•A summary across all folders, showing items processed in green, items discarded without having to open the FS in yellow, and items discarded after opening the FS in red.
•An analysis for each TOSEND folder of the outcomes of scanning. These bar-charts show counts in the following categories:
•Process: FS files assigned to a channel for processing (including the for processing of errors).
•Pre-process: items moved to PREPROC for external processing, or for which an external pre-process was spawned.
•Not Ready: FS files found with a future datestamp and not opened.
•Suspended: FS files identified by their FS number as part of a suspended job, and not opened.
•Active: FS files found to be active on this or another node, and not opened.
•Error: FS files discarded after opening because an error or misconfiguration prevented assignment to a channel.
•Domain Limit: FS files discarded after failing a domain limit check.
•Phone Mask: FS files discarded after matching an exclusion phone mask.
•Busy Phone: FS files discarded after failing on a self-busy check.
•Suspended: FS files discarded after checking the job status.
•Send Time: FS files discarded after checking the fax send time, and being written back with a future timestamp.
•No Channel: FS files which could not be processed for lack of a suitable free channel to handle them, but without a $fax_send_channel restriction.
•Send Channel: FS files which could not be processed for lack of a suitable free channel to handle them, in the presence of a $fax_send_channel command.
The period covered by the analysis depends on the system load but should cover up to the previous hour on a rolling basis.
Note that the unprocessed files may have higher counts because they have been scanned many times during the period covered by an analysis window, whereas each 'processed' file is only counted as processed once, by definition.
This feature is currently experimental and is subject to change.
The 'c' key (lower case C)writes to the engine trace file a list of the current state of each channel and whether it is currently connected to a telephony channel or processing an FS file.
