5.1 About the OFSBD Job Protocol
The system initiates all OFSBD jobs by using a standard operational protocol that
utilizes each job’s metadata, which resides in a standard set of database tables. OFSBD
Job Protocol processes include the following:
Dispatcher:Polls the job metadata for new jobs that are ready for execution. This daemon process starts a MANTAS process for each new job.Mantas:Creates a new job entry based on a template for the job that has the specific parameters for this execution of the job (that is, it clones a new job).
Table 5-1 OFSBD Job Protocol Shell Scripts
| OFSBD Job Protocol Process Shell Script | Description |
|---|---|
| start_mantas.sh | Starts all OFSBD jobs. This script invokes the cloner and MANTAS processes. This is the integration point for a third-party scheduling tool such as Maestro or AutoSys. |
| start_chkdisp.sh | Calls on the check_dispatch.sh script to ensure that the dispatcher runs. |
| stop_chkdisp.sh | Stops the dispatcherprocess. |
| restart_mantas.sh |
Changes job status codes from the ERR status to the RES status so that the dispatchercan pick up the jobs with the RES status. |
| recover_mantas.sh | Changes job status codes for jobs that were running at the time of a
system crash to the ERR status. After running this script, the
restart_mantas.shscript must be run to change the
ERR status code to RES in order for the dispatcherto be able to
pick up these jobs.
|
In the OFSBD Job Protocol, the processes use a variety of metadata that the OFSBD database provides. Some of this metadata specifies the jobs and their parameters that are associated with the regular operations of an OFSBD installation. Some of this metadata captures the status of job execution and is useful for monitoring the progress of an OFSBD operational cycle.
This section covers the following topics: