User Guide > Objects > Alphabetical Listing > Sync Tab

Sync Tab

The Sync tab is object-type specific and is available in all executable objects.

Sync objects synchronize task on the basis of defined conditions. Enter one or several Sync objects including the actions that should be taken in this tab if you want to make use of this possibility.

The Sync objects are checked one after the other when the task starts. The Automation Engine tries to use the Sync object of the first line by calling the start action. If this is not possible because this is not allowed by the Sync object's current condition, the task waits, aborts or is skipped. The type of reaction depends on the Else condition defined in the tab's last column. If "wait" has been specified, the task waits until it can use the Sync object with the start action. Then the Automation Engine checks the Sync object in the next line etc. The task starts as soon all Sync objects could successfully be used. Depending on the task's end status, either an abend or end action is processed.

Up to 500 Sync objects can be specified.

All Sync objects must not include a total of more than 5000 rules. Rules are defined actions that are specified directly in the Sync object.

Task ends are administered by work processes but only the primary work process releases busy Sync objects. Because of this task allocation, it can take several seconds until a Sync object is released after a task has ended. In this case, the report entry includes a time stamp that shows a time that is later than the task has ended. Such delays occur when the primary's work load is high or if it is processing lots of Sync objects.

Note that using many Sync objects and rules can reduce task clarity. Automic recommends reducing the number of Sync object to a minimum.

Description

Only actions that have been defined in the Sync object can be selected.

Field/Control	Description
Sync object	Selects the Sync object that should be used to synchronize the task.
Start action	Defines the action that should be taken when the task starts. If this is not possible because of the Sync object's status, the Else condition becomes effective.
Abend action	This action is processed if the task aborts.
End action	This action is processed if the task ends successfully.
Else	You can define here what should happen to the task if the start action cannot be executed: The task should wait until the start action can be executed (WAIT). The task aborts (ABEND). The task is skipped (SKIP).