With this job type, ibaDatCoordinator monitors one or more directories in which DAT files are stored. Monitoring is performed either via file system monitoring or by regularly scanning the directories. As soon as ibaDatCoordinator detects a new, unprocessed DAT file, the job starts processing the defined tasks.

During execution, ibaDatCoordinator monitors the status of tasks within a job and marks DAT files that have already been processed. For this purpose, info fields are added to each DAT file, which show whether a job has been fully processed or has failed, and how many attempts at processing have already been made. When you open a processed DAT file in ibaAnalyzer, you will find the info fields $DATCOOR_status and $DATCOOR_times_tried in the info section of the data file.

A job is considered failed if at least one of its tasks could not be executed. As long as a job is not fully completed, ibaDatCoordinator will try to repeat the job.

Note
	When a job is repeated, all of its tasks are executed again, including those that have already been successfully completed.

In the job configuration, you can specify how long and how often DAT files whose processing has failed are reprocessed. If the maximum number is exceeded, ibaDatCoordinator permanently marks the files as failed. You can then decide whether to delete these files or reset the status information to enable reprocessing.

You can find out how to configure jobs in ibaDatCoordinator in Configuring a job. A description of the specific configuration options for the DAT file job can be found in DAT file job – settings.