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 to be taken in this tab if you intend to use this possibility.

The Sync objects are checked one after the other when the task starts. The Automation Engine tries to allocate the Sync object of the first line by calling the start action. If this is not possible due to the Sync object's current status, the task waits, aborts or is skipped. The particular 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 as all Sync objects could successfully be allocated. Depending on the task's end status, either an abend or end action is processed.

Up to 500 Sync objects can be specified.

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

Task ends are administered by work processes but only the primary work process releases busy Sync objects. Due to 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 shows a time stamp which is later than when 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. Therefore, Automic recommends keeping the number of Sync objects to a minimum.

Description

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

Field/Control	Description
Sync object	Selects the Sync object to be used for synchronizing the task
Start action	Defines the action to be taken at task start. If this is not possible due to the Sync's status, the Else condition becomes effective.
Abend action	This action will be processed if the task aborts.
End action	This action will be processed if the task ends successfully.
Else	Define what should happen to the task if the start action cannot be executed: Task should wait until the start action can be executed (WAIT) Task aborts (ABEND) Task is skipped (SKIP)