Defining downtime

During planned downtime neither users nor jobs should use the system. You can plan your work in such a way that no long running tasks or jobs are started before the downtime. Running jobs are killed when the system is brought down and this can cause issues.

To define the downtime period, you must specify this information:

• Upgrade Date/Time

  Specify the start date/time of the downtime period. Jobs are not started if they, based on their expected duration, would still be running at the start of the downtime period.

  The calculation of the expected duration of a job is based on the recorded history of that job. Only the history with status (‘cause’) ‘Executed’ is taken into account because these records give the total time required to successfully run the job.

• End Period

  Optionally, specify the end date/time of the downtime period. If you specify the End Period, jobs are also not started between the Upgrade Date/Time and the specified end time.

After the downtime period, the jobs that should have started during the downtime period are automatically scheduled to start directly.