34.2 Setting up FrameMaker for unattended operation

Before you can use runfm, you must set up FrameMaker for automatic operation. Execute the following command, either in a command window or via Start > Run...:

"path\to\FrameMaker" -progid:FrameMaker.M2G -auto

where:

path\to\	is the location where FrameMaker is installed on your system; enclose the entire path and file name in double quotes if the path contains any spaces; you can omit the path if FrameMaker is on your system execution PATH
-progid	is a required RPC (Remote Procedure Call) server identifier; for using runfm, the default identifier is FrameMaker.M2G.; the colon between -progid and the identifier is required
-auto	allows runfm to start FrameMaker from the command line; without this option, FrameMaker must already be open for runfm to work.

After you set up FrameMaker this way, you can use runfm to run, from a command line, any FrameMaker plug-in that is set up to receive RPC notifications.

Despite its name, the -progid option has nothing to do with which FrameMaker plug-in you want to run. You can provide any string as the value for -progid, as long as you start FrameMaker with that string first, then specify the same value when you execute runfm. If you specify -progid:FrameMaker.M2G when you set up FrameMaker, you can omit this option entirely when you use runfm to run Mif2Go.

These settings become effective after you exit FrameMaker. Once set, they remain set in the Windows Registry (in HKEY_LOCAL_MACHINE/Software/Classes), until/unless you set up FrameMaker again, perhaps with a different value for -progid.

See also:

§34.4 Using runfm for Mif2Go conversions

§34.8 Using runfm for other FrameMaker plug-ins

---

> 34 Converting via runfm > 34.2 Setting up FrameMaker for unattended operation