Omni Systems, Inc. Mif2Go User's Guide, Version 55

<< Prev | Next >>

> 36 Converting via runfm > 36.5 Troubleshooting runfm processes > 36.5.3 Reviewing FrameMaker console messages after runfm

### 36.5.3 Reviewing FrameMaker console messages after runfm

When you specify -close all for the runfm command (or for the last in a series of runfm commands), provided you are not operating runfm across a network (see §36.7 Operating runfm across a network), before FrameMaker closes, runfm appends the contents of the FrameMaker console window to a text file, default name mif2go.log (see §36.5.2 Capturing console diagnostics: runfm -log option), located in the input directory for your project. You should inspect this file for error messages.

If you do not use the -log option, after FrameMaker closes (and before you open it again) you can find the console output for the latest FrameMaker session in consfile.txt, located in the FrameMaker installation directory.

Some kinds of errors are not reported

The Mif2Go Export and Finished dialogs are suppressed by runfm, to make sure Mif2Go does not request user intervention during an unattended conversion. If any FrameMaker file that Mif2Go tries to access during the conversion (such as a chapter file in a book) has a problem (such as missing fonts or graphics) that would normally result in a dialog, the problem is ignored and the conversion continues. Such problems are not reported in the FrameMaker console window; with unattended operation, you have no way to know they occurred. Therefore it is essential to make sure your conversion project is thoroughly debugged before you use runfm for unattended operation.