5.3.3 Restarting a Job

If the dispatcher stops, all jobs stop. You must restart the dispatcher and restart all jobs, including the job that generated real errors.

Restarting a job is necessary when one or both of the following occurs:

• The dispatcher generates errors and stops during MANTAS processing. When the dispatcher is running, the OFSBD administrator can restart a job (or jobs) by changing each job’s status code from ERR to RES.
• A job generates errors and stops during MANTAS processing. If a job stops processing due to errors, correct the problems that caused the errors in the job run and restart the job.

Note:

If the dispatcher has stopped, you must restart it.

To restart a job, follow these steps:

1. Type restart_mantas.sh <template group id> at the system prompt.
2. Press Enter.
   When the dispatcher picks up a job from the job queue that has a code of RES, it automatically restarts the job (Refer to Starting Behavior Detection Jobs). By default, the restart_mantas.sh script looks for jobs run on the current day.
   To restart a job that was run on a specific date, you must provide the optional date parameter such as restart_mantas.sh <template group id> <DD-MON-YYYY>.