I have several jobs that hang on the terminal emulator, despite the fact that their definition directs the output to file (or trash or whatever).

Does anybody have an extremely clever method of monitoring vtemulator output or another proven method of troubleshooting this nuisance?

Francesco,

I never tried with Terminal emulator in jobs but I have other programs which use that.

Can you please explain your design/requirement more to understand ?

In the job/batch mode the UI options are not supported. Did you use the shell() command with the options -
SHELL_BACKGROUND
Background processing. No main window is created and the process produces no output. This is similar to SHELL_NO_OUTPUT + SHELL_NO_WAIT.
SHELL_NO_WAIT The shell function does not wait for the emulator to end. This is useful for starting shell processes (such as an editor) while continuing processing. The variable shell.pid is set to the process number of the activated terminal emulator process. A new main window is created.

SHELL_NO_OUTPUT The terminal emulator does produce any output. This implies the SHELL_NO_MWINDOW option.

or you can also use the run.prog() or run.baan.prog() with the options - RP_NOWAIT run as a background program

So I know, its really not my problem...but I can't help myself.