About local jobs on Windows

You can include a local job in the flow diagram.

A local job is a job that will execute immediately on the Process Manager host without going through LSF®. A local job is usually a short and small job. It is not recommended to run long, computational-intensive or data-intensive local jobs as it can overload the Process Manager host.

A local job is blocking: each local job has its own thread for execution, but the dedicated local job thread will not be freed up to execute another local job until the local job that is executing has completed.

Controlling a local job

You cannot directly kill a local job in the same way as you kill any other job. The local job can only be killed as a result of the flow being killed, or if it runs for longer than the configured timeout value.

If you suspend or resume a flow that contains local jobs, the local jobs will be killed and rerun.

You can view a local job’s runtime attributes in Flow Manager. Note, however, that no resource usage is a available for the local job.

Parameters related to local jobs

By default, a local job has a timeout so that it will be killed if it was running for too long. The parameter JS_LOCAL_EXECUTION_TIMEOUT in js.conf defines how long a local job is allowed to run before it is killed by the system.

For security reasons, you may want to disable local jobs altogether. You can disable local jobs by setting the parameter JS_LOCAL_JOBS_LIMIT=0 in js.conf.