Source:Special Schedules: Difference between revisions
(Priority higher then prio of 'to be suppressed' one) |
(revised jpegs) |
||
Line 9: | Line 9: | ||
An hourly schedule Backup_ORACLE with command event ORACLE_PROD and Priority '1' is already defined. | An hourly schedule Backup_ORACLE with command event ORACLE_PROD and Priority '1' is already defined. | ||
To disallow execution during 12:00 till 14:00 o'clock another schedule | |||
* weekly execution, from Monday | To disallow execution during 12:00 till 14:00 o'clock another schedule, e.g. block_ORACLE_1200-1400, must be defined with | ||
* weekly execution, from Monday till Friday | |||
* starting time 12:00 o'clock, duration 2 hours. | * starting time 12:00 o'clock, duration 2 hours. | ||
[[Image:Blocking_schedule_execution_schedule.jpg|center]] | |||
This schedule, e.g. block_ORACLE_1200-1400 must be connected to the same command event, e.g. ORACLE_PROD, | This schedule, e.g. block_ORACLE_1200-1400 must be connected to the same command event, e.g. ORACLE_PROD, | ||
Line 17: | Line 20: | ||
and the execution parameter ''''Blocking Date'''' ('Sperrtermin') must be enabled. | and the execution parameter ''''Blocking Date'''' ('Sperrtermin') must be enabled. | ||
[[Image: | |||
[[Image:Blocking_schedule_execution_params.jpg|center]] |
Revision as of 14:11, 4 August 2008
Special Schedules
In version 3.4.1.x a special version of programm sm_sepul_event revision 1.183.2.1 allows to define schedules which will block hourly execution of other schedules related to the same object. The blocking is done during the 'starting time window' of a further defined schedule.
Example:
An hourly schedule Backup_ORACLE with command event ORACLE_PROD and Priority '1' is already defined.
To disallow execution during 12:00 till 14:00 o'clock another schedule, e.g. block_ORACLE_1200-1400, must be defined with
- weekly execution, from Monday till Friday
- starting time 12:00 o'clock, duration 2 hours.
This schedule, e.g. block_ORACLE_1200-1400 must be connected to the same command event, e.g. ORACLE_PROD, his priority must be higher then the other one, e.g. '2' and the execution parameter 'Blocking Date' ('Sperrtermin') must be enabled.