Cisco Cisco Workload Automation 6.3 User Guide
135
Jobs and Job Groups
Life Cycle of a Job instance
(History Retention) is located on the Options tab of the Job Definition dialog of each job in question. You can have
different settings for different jobs. For example, Job A could have instances kept for 30 days, while Job B could
have instances kept for 60 days.
different settings for different jobs. For example, Job A could have instances kept for 30 days, while Job B could
have instances kept for 60 days.
Future days to include in Schedule – Defines how far in the future to schedule jobs. For example, if this setting is
set to three days and today is June 1st, you can view jobs in the production schedule out to June 4th. Set the number
of future days to include in the production schedule on the Master tab of the System Configuration dialog.
set to three days and today is June 1st, you can view jobs in the production schedule out to June 4th. Set the number
of future days to include in the production schedule on the Master tab of the System Configuration dialog.
When you create a job or job group with a calendar that specifies a date within the current production schedule range
and click OK, the Effective Date dialog displays to choose the date to begin running the job or job group. Each day,
the automatic compilation process compiles incrementally for the next leading day, checking the calendar
information of each job or job group to see if it should run on that day.
and click OK, the Effective Date dialog displays to choose the date to begin running the job or job group. Each day,
the automatic compilation process compiles incrementally for the next leading day, checking the calendar
information of each job or job group to see if it should run on that day.
Note: Because only the leading date of the production schedule (or forecasted schedule) is compiled automatically,
if you choose not to schedule a job or job group using the Effective Date dialog, the job or job group will only enter
the schedule on the next compile. For example, if Job D is scheduled to run daily, you can choose Cancel from the
Effective Date dialog, and if the production schedule presently spans11/1/04 to 11/5/04, the job or job group will
be scheduled to run starting on 11/6/04.
if you choose not to schedule a job or job group using the Effective Date dialog, the job or job group will only enter
the schedule on the next compile. For example, if Job D is scheduled to run daily, you can choose Cancel from the
Effective Date dialog, and if the production schedule presently spans11/1/04 to 11/5/04, the job or job group will
be scheduled to run starting on 11/6/04.
If you want to remove the job from the production schedule, you can disable the job from the Jobs pane by
right-clicking it and selecting the Enable option from the context menu. You can also right-click it from the Job
Activity pane and select the Remove Job(s) from schedule option from the context menu.
right-clicking it and selecting the Enable option from the context menu. You can also right-click it from the Job
Activity pane and select the Remove Job(s) from schedule option from the context menu.
Automatic Daily History Cleanup – If you are automatically creating production schedules, you should also
automatically clean up the production history. This option ensures that the CWA automatically purges outdated job
history data from the system database. When it is time to purge data (by default at the beginning of the production
day), CWA looks for all job information that is older than the retention history settings. If this option is not selected,
you must manually purge the database of outdated job information at regular intervals by scripting.
automatically clean up the production history. This option ensures that the CWA automatically purges outdated job
history data from the system database. When it is time to purge data (by default at the beginning of the production
day), CWA looks for all job information that is older than the retention history settings. If this option is not selected,
you must manually purge the database of outdated job information at regular intervals by scripting.
Life Cycle of a Job instance
This section covers these topics:
About the Job Instance Life Cycle
Each CWA job instance has its own life cycle in the production schedule. The job’s current status indicates where it is in
its life cycle. A typical life cycle is one where the job:
its life cycle. A typical life cycle is one where the job:
Waits in the production schedule for its dependencies to be met.
Enters a queue and waits for an execution slot to become available.
Launches on its designated agent.
Starts execution successfully on its designated agent.