The activation of each job depends on the scheduling parameters defined for it. As in the case of job networks, earliest starting time can be defined.
16.02.15 ***** Entire Operations ***** 17:23:02
Job Maintenance Owner EXAMPLE Network B60-FLOW Version
+-------------------------------------------------------------------------+ -
| |
| Scheduling Parameters |
| Job JOB-012 |
| |
| Estimated Elapsed Time ==> _________ Min. Average ==> 0.00 |
| History Elapsed Time ==> 0.00 0.00 0.00 0.00 |
| 0.00 0.00 0.00 0.00 |
| |
| |
| Earliest Start Time ==> ________ ___ days later |
| Latest Start Time ==> ________ ___ days later |
| Deadline Time ==> ________ ___ days later |
| |
| Schedule Dependency ==> N |
| | *
| ---PF1---PF3------------PF5----------------PF9---PF10---PF11---PF12-- |
| Help End Save LMsg Acct ScDep Menu |
+-------------------------------------------------------------------------+
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Add End Save Up Down Menu |
For jobs, however, the user can additionally specify whether a scheduled job that did not run (e.g. due to hardware problems) is to be rescheduled (i.e. the job is scheduled to run twice at the next scheduled time). A number of days can also be specified to determine how long a job can reside at most in the active queue before it is executed.
The user can also specify an estimated job running time which the Entire Operations Monitor uses to calculate starting and end time for the job. This can prevent a job from running if a predefined deadline would be exceeded.
The job scheduling parameters also provide a facility to notify specified users if the start of job fails to meet the defined deadline starting time.
For detailed information, see the section Scheduling a Job in the User's Guide.