Troubleshooting and FAQs › Frequently Asked Questions › Stopped Jobs

Stopped Jobs

What happens if some jobs are running in the manager when the manager fails or is stopped?

After the manager starts a job, the job is an independent process that continues to run even if you stop the manager with the SCHEDULE STOP command.

• If you restart the manager before the job completes, all is normal.
• If the job completes while the manager is stopped, the termination message with the accounting information is not written to the manager’s mailbox, and the database is not updated. The job remains marked as running on the current node and process (PID).
• When the manager restarts, it reads through the database and verifies that all jobs marked as currently running are actually running. If the manager finds a job that is not running even though the database entry says it is, then the current time and date are filled in and the completion status is changed to:

  	NSCHED-F-ABORTED, Job was aborted
  

  This is a failure status. Any mail or broadcast notification is sent at this point. If the SET RESTART command is enabled for that job, then the job runs again. Otherwise, the job is put on hold.

Whenever I stop and restart the manager, it creates a file named your-system-name_REMOTE.LOG. Is this normal?

Job Management Manager commands that come from outside your cluster are run by the SCHED_REMOTE process. This process receives DECnet connects, validates proxy accounts, and writes information to NSCHED$:NODE_REMOTE.LOG to provide an audit trail of remote activity. When the SCHED_REMOTE process starts, an empty file is created.

You can edit the Job Management Manager startup procedure not to start the SCHED_REMOTE process if all of the following are true:

• You do not want to use Job Management Manager commands on remote nodes.
• The remote nodes do not need to communicate with you.
• You do not have any jobs on your cluster that depend on remote jobs.