Cisco Cisco Workload Automation 6.3 User Guide
133
Jobs and Job Groups
Overview
Scheduled vs. Unscheduled Jobs
Jobs and job groups can run either automatically on a regular schedule when you assign a calendar or on an unscheduled
basis whether or not it has an associated calendar. For example, a job could run automatically on the 1st and 15th of
every month. The job could also be inserted into the schedule as needed throughout the month. When a calendar is not
assigned, the job will only run when you manually insert the job into the schedule. Calendars are created from the
Calendars pane and can be applied to a job or job group from the Job Definition or Job Group Definition dialog.
basis whether or not it has an associated calendar. For example, a job could run automatically on the 1st and 15th of
every month. The job could also be inserted into the schedule as needed throughout the month. When a calendar is not
assigned, the job will only run when you manually insert the job into the schedule. Calendars are created from the
Calendars pane and can be applied to a job or job group from the Job Definition or Job Group Definition dialog.
Job, File, Variable and Time Dependencies
You can create job dependencies, file dependencies, variable dependencies and time dependencies for a job or job
group.
group.
A job dependency is a dependency on another job reaching a certain status. For example, you can set a job to run only
after a previous job has completed normally.
after a previous job has completed normally.
A file dependency is a dependency on the existence of a file, on whether or not a file has been modified, or on the size
of a file. This feature ensures that your jobs run when the appropriate data is available.
of a file. This feature ensures that your jobs run when the appropriate data is available.
A variable dependency is a dependency on the value of a variable. You can use a preset CWA variable or define your
own. Variables can be used to track resource usage and can be updated automatically using variable update actions. For
more information about variable update actions, see
own. Variables can be used to track resource usage and can be updated automatically using variable update actions. For
more information about variable update actions, see
A time dependency sets a specific time window for the job to run.
Intermaster Dependencies
You can implement intermaster dependencies by combining different CWA tools and areas of functionality, such as job
events. The methodology can be extended to apply to dependencies between any number of jobs on any number of
masters. For more information on intermaster dependencies, see
events. The methodology can be extended to apply to dependencies between any number of jobs on any number of
masters. For more information on intermaster dependencies, see
.
Job Events
Job and job group definitions can include exception-based actions triggered by job events. These actions can provide
different types of notification as well as perform some additional task(s) in response to certain conditions. For example,
a job event could be defined for a job that completes abnormally or when a job stops. You can associate one or more
job events with a job. You can also assign multiple actions to each event. For more information about job events and
actions, see
different types of notification as well as perform some additional task(s) in response to certain conditions. For example,
a job event could be defined for a job that completes abnormally or when a job stops. You can associate one or more
job events with a job. You can also assign multiple actions to each event. For more information about job events and
actions, see
System Events
CWA also watches for system events, such as when the master stops or when the production schedule finishes
compiling. Job and system events can then trigger actions in response to the event condition. Job events can also be
defined at a system level so that any job will trigger a set of actions when a particular job event occurs. For example,
CWA can email you if any job runs longer than a predefined maximum allowable time.
compiling. Job and system events can then trigger actions in response to the event condition. Job events can also be
defined at a system level so that any job will trigger a set of actions when a particular job event occurs. For example,
CWA can email you if any job runs longer than a predefined maximum allowable time.
Actions
CWA can respond to events using multiples and combinations of the following action types:
Email – Notifies you and/or others of your job event via email.
SNMP – Sends SNMP messages to SNMP managers that monitor network activity.
Alert – Sends an alert message to the operator’s console regarding the event.
Job Control – Performs job control, such as stopping an active job, or rerunning a job that completed abnormally.