Home › Forums › Mif2Go › Automation

After runfm PDF output, frame is "Not Responding" for a long time

Wed, 08/22/2012 - 4:04pm — flatironssolutions

Hello,

We have an automation process that executes runfm -pdf , etc, for a number of frame files. The PDF distiller runs and completes, but then Framemaker "hangs" for a minute or so until it finally exits. The frame files are various lengths and complexities roughly 20-80 pages each. The behavior is the same for any file size.

Is this normal? I have tried the PDF output with both the .fm and the mif format files, and both have the same behavior.

The CPU is minimal also, so I'm not sure what is happening.

Also, I create a mif file during a separate pass/runfm execution, and that runs and exits quick. I believe this eliminates any spin locking or deadlocking waiting on a resource from the java based executor.

Thanks for any responses, it is strange that frame just seems to hang up for a while before finishing with the PDF.

Wed, 08/22/2012 - 5:22pm — drpadmin

Automation on a server

Back on July 31, we warned you about a problem that sounds like this one:

The only possible problem with your setup is that Frame's PDF generation always puts the PDF in My Documents for the current user. So we watch that folder, and move it to the requested destination when it stops changing size. If you are using FrameServer, it might be putting the PDF somewhere else...

In which case, you are experiencing the delay we allow for it to finish. You do get the PDF delivered to the folder where you wanted it, right?

Wed, 08/22/2012 - 10:06pm — flatironssolutions

much better now

Dough!

and I was wondering earlier why there was a browse button if the only two choices for destination were Prompt and Documents\*.pdf.

I browsed and set the dir, and since it doesn't have to wait, it is quick.

Sorry for re-asking, but thanks again for the help!