UNICOM Intelligence Load Tool uses the Log component to generate debugging messages about the tests you are running. These messages are displayed on the Logging tab and are written to a MRI*.tmp log file as well.

The amount of detail displayed depends on the logging level check boxes you have selected (see Logging levels for details). In the log file, this is controlled by the registry keys for the Logging component and uses MRI as the log group name.

See also Registry keys for the Logging component.

Answers generated by the Auto Answer player are always logged at the Info level. The log reports the following information for each interview:

The MRI log files are very useful for debugging errors. Open the file using DM Query and find the errors. Then use the Interview ID and possibly other information to correlate the error messages with those in the IVW file and with the case data to investigate why the error might have occurred.

To clear the Logging tab without affecting the contents of the logging file, click Clear.

Pausing logging temporarily prevents UNICOM Intelligence Load Tool from writing to the Logging tab, allowing you to scroll through the current display without changing anything. The test continues running and, if appropriate, writing to the logging file. When you restart logging, UNICOM Intelligence Load Tool updates the Logging tab with any information generated while display updating was paused.

Click Pause to suspend logging and then click it again to restart logging.

When you are running more than one test concurrently you can choose which tests you want to see reported on the Logging tab. The default is to view details for all tests that are running. To change this so that only certain tests are reported, proceed as follows: