Abort Mode and Commit Type Combinations

The following table provides an overview of all possible combinations of the Abort Mode setting of a task and the Commit Type of a task. 'Yes' means a possible combination.

Abort Mode	Commit Type	Action task	Export task	Import task	Job task	SQL task
None	None	Yes	-	Yes	Yes	Yes
None	Record	-	-	Yes	-	Yes
None	Task	Yes	-	Yes	Yes	Yes
Task	None	-	-	Yes	-	Yes
Task	Record	-	-	Yes	-	Yes
Task	Task	-	-	Yes	-	Yes
Job	None	-	Yes	Yes	Yes	Yes
Job	Record	-	-	Yes	-	Yes
Job	Task	-	Yes	Yes	Yes	Yes

Action tasks are always considered successful, the Abort Mode can therefore only be 'None'. The commit type can be: None, or Task.

In export tasks, constraint errors can not occur, so all errors are considered to be fatal errors: You can only specify 'Abort Job on Error'. The commit type can be: None, or Task.

•None: when a non-fatal error occurs during the import of a record, the error is reported and the import of the record is considered to have failed. The remaining SQL statements of the import task are not executed anymore for that record, but the import task and the job continues.

•Abort Task on Error: when a non-fatal error occurs during the import of a record, the error is reported and the import of the record is considered to have failed. The import task stops, but the job continues with the next task.

•Abort Job on Error: when a non-fatal error occurs during the import of a record, the error is reported and the import of the record is considered to have failed. The import task stops and the job is considered to have failed.

For job tasks, the Abort Mode can be 'None' (when the job called exits with a non-fatal error, the job continues normally), or 'Abort Job on Error'. The commit type can be: None, or Task.

•None: when a non-fatal occurs, the error is reported. Subsequent statements of the task will be executed

•Abort task on error: when a non-fatal occurs, the error is reported. Subsequent statements of the task will not be executed. Remaining tasks will be executed.

•Abort job on error: when a non-fatal occurs, the error is reported. Subsequent statements of the task will not be executed. Remaining tasks will not be executed. The job is considered to have failed.