Cisco Cisco Workload Automation 6.3 User Guide

Jobs and Job Groups

Setting Dependencies on Jobs

Master2

On Master2, create a string variable called master1_joba and create a variable action to initialize it to blank 
whenever JobB is added to the schedule.

On Master1, associate the job created in step 2 with a job action, and associate that action with a job event triggered 
by JobA completing normally. To make it easier to work with multiple jobs, create one linking job as in step 2 and 
override the command parameters here.

On Master2, add a variable dependency to JobB so that JobB depends on master1_joba = “normal”.

When JobA completes normally, it triggers the linking job that sets the master1_joba variable value on the other 
master to satisfy JobB's dependency.

The actions and events used in this scenario can be defined generically for reuse in working with any number of jobs that 
have inter-master dependencies. The CWA API can also be used to set CWA variables on any master programmatically. 
For more information on the CWA API, see the CWA API Guide. 

Setting Dependencies on Jobs

Job Dependency Definition Dialog

The Job Dependency Definition dialog displays when you add or edit a job dependency from the Dependencies tab of 
the Job or Job Group Definition dialogs.

Note: For instructions on how to implement inter-master dependencies, see 

.

This dialog contains the following elements:



Job/Group – The job(s) or job group(s) that the current job depends on. You can search for jobs or job groups by 
clicking the Browse button, which opens the Job Search dialog. You can also view a job/group drop-down list by 
clicking the down-arrow button. If you narrowed your search for jobs using the Job Search dialog, the list displays 
the subset of jobs found. Otherwise it displays all jobs you or your workgroups own. 

If you choose more than one job or job group, dependencies will be created for each one selected, and when you 
click OK, they appear on the Dependencies tab. You can then update individual job dependency criteria by 
double-clicking them from the Dependencies tab

. 

Note: You cannot type a job or job group name in this field directly.



Operator – Defines whether the dependency should be satisfied when the preceding job equals or does not equal 
the specified status.



Status – The status of the job dependency. Select

 Launched, Active, Completed Normally, Completed Normally 

(Output Pending), Completed Abnormally,

 Completed Abnormally (Output Pending), Error Occurred, Externally 

Defined, Externally Defined (Output Pending) or

 Completed as the condition for which the job dependency is 

satisfied.



Occurrence – Used if the job dependency is a job that repeats within a production day. 

Select First Occurrence when the first instance of the job should be used to satisfy the dependency. 

Select Last Occurrence when the last instance of the job should be used to satisfy the dependency.If the job 
does not repeat, the last instance of the job dependency is used. If the dependent job has more repeating 
instances, the last instance of the job dependency is used to satisfy the dependency for the trailing instances 
of the dependent job.