## 36.7 Operating runfm across a network

To use runfm on a network with FrameMaker on a different system, you must observe the following restrictions:

• the system where FrameMaker and Mif2Go are installed must be in the same domain as the system where you are using runfm

• you must be logged into both systems with the same user ID

• FrameMaker must be already open on the remote system.

Specify -remote for network operation

To operate runfm across a network, specify -remote with the name of the remote system where FrameMaker is installed. The name to use for the remote system is the name you see under My Network Places in Windows Explorer. Omit any punctuation.

Use FrameMaker CLSID for -progid

For -progid you must supply the automatic FrameMaker progid, which is the CLSID (class identifier) found in the remote-system Windows Registry for the following key:

HKEY_LOCAL_MACHINE/Software/Classes/FrameMaker.Api

Enclose the CLSID in braces; for example:

-progid {539DB5D0-C0C6-11D0-985E-0060970BEC0B}

No log file with remote operation

When you specify -remote you can use the -close option, but if you -close all, runfm does not copy the FrameMaker console output to a log file (see §36.5.3 Reviewing FrameMaker console messages after runfm).

Set up both systems for DCOM

For remote operation you might have to specify system settings to enable DCOM (Distributed Component Object Model) on both machines. On Windows XP Pro (for example), type dcomcnfg at a command prompt and press Enter; the Component Services console opens. Navigate to Component Services > Computers > My Computer > DCOM Config, and select FrameMaker API. On the Action menu choose Properties; the FrameMaker API Properties dialog opens. For information about the settings available, try Help. For additional information, see Running asynchronous clients on remote hosts in the FDK Platform Guide, winguide.pdf.

| 36.6 Comparing runfm with the DCL command-line filter |  | 36.8 Using runfm for other FrameMaker plug-ins |