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

> 36 Converting via runfm > 36.5 Troubleshooting runfm processes > 36.5.2 Capturing console diagnostics: runfm -log option

### 36.5.2 Capturing console diagnostics: runfm -log option

If you are using runfm on the same system as FrameMaker, before closing FrameMaker runfm appends the contents of the FrameMaker console window to the file specified by the -log option; this file is placed in the same directory as the specified book or document. The default log file name is mif2go.log. If you specify both -book and -doc, and the book and document files are in different directories, the log file is placed in the document directory rather than the book directory.

The contents of the FrameMaker console window are appended to the log file only when you specify -close all (see §36.4.4 Closing FrameMaker files after conversion); if FrameMaker remains open after runfm finishes, nothing is appended to the log file.

If you are using runfm across a network, the -log option has no effect; see §36.7 Operating runfm across a network.

Maintaining a log file preserves FrameMaker console output over multiple executions of runfm, because FrameMaker clears the console each time it starts. See §36.5.3 Reviewing FrameMaker console messages after runfm.

See also:

§36.4.4 Closing FrameMaker files after conversion

§36.5.1 Increasing console diagnostics: runfm -diag option

§36.5.3 Reviewing FrameMaker console messages after runfm

> 36 Converting via runfm > 36.5 Troubleshooting runfm processes > 36.5.2 Capturing console diagnostics: runfm -log option

| Mif2Go User's Guide: 36.5.1 Increasing console diagnostics: runfm -diag option |  | Mif2Go User's Guide: 36.5.3 Reviewing FrameMaker console messages after runfm |