Asset Management › Asset Jobs › New Job Wizard › Scheduling Options Dialog › Scheduling Options Dialog: Dependency Tab

Scheduling Options Dialog: Dependency Tab

The Dependency tab lets you specify the factors based on which the job should execute at the scheduled time.

This tab contains the following fields:

Job Dependency

Run job only if the status of the job below is OK

Runs the job only if the status of the given job is OK. This option is useful when the job to be carried out is dependent upon the successful completion of another job. You can select the latter from the list box, which lists all the jobs defined in the domain.

Example: Assume that you are doing a software distribution job in stages as described here:

1. Copying all new files in a zip file (low network traffic).
2. Unzipping all files and placing them in the correct directories.
3. Making groups in Windows and creating icons.

   If stage 1 fails, or if the user says No when prompted, stages 2 and 3 should not be executed.

Job is attached to, and executed on related asset

Runs the job only on completion of the job on a related asset. This works in the following way:

• If the current job is attached to a workstation, for example, a Computer, the dependant job should first have been executed on the linked user.
• If the current job is attached to a user, then the dependant job should first have been executed on the linked computer.

File Dependency

Run job only if...

Lets you select the following file dependency factors, when selected:

The following file exists

Executes an action depending on the existence of the selected file. You can select the file by typing the path and file name or by browsing in the File Text Field and Browse Button fields.

The following file does not exist

Executes an action depending on the non-existence of the selected file. Enter the name of the non-existing file in the File text field.

File text field and Browse button

Defines the file name and path on which the job is dependent. You can either enter or browse for the existing file. Clicking the Browse button opens the Select File dialog.

Note: Browsing is done on the manager, but the file you want to select as a dependency must exist on the agent system. If the file does not exist on the manager, you must enter the file path name instead of browsing for it.

Job Concurrency Limit

Allow only <n> execution at a time

Specifies the maximum number of simultaneous executions of an action per Scalability Server. If the agent belongs to a large Scalability Server and all other agents must be updated, set a maximum number of simultaneous executions, to distribute the network load over a period.

More information:

Scheduling Options Dialog: Pre-Job Tab