| Title: | SCHEDULER |
| Notice: | Welcome to the Scheduler Conference on node HUMANE ril |
| Moderator: | RUMOR::FALEK |
| Created: | Sat Mar 20 1993 |
| Last Modified: | Tue Jun 03 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1240 |
| Total number of notes: | 5017 |
This customer likes the product but he has a lot of improvment requests. He sent me the following mail. But this seems not to be the prefered behavior or ? Is there anyone who can explain it to me. Regards Sten Lindstrom TSC Sweden ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ There is currently a functional "peculiarity" involving dependencies between jobs. Let us assume the following situation: JOB_20 depends on JOB_10 (JOB_10 --->--- JOB_20) JOB_10 is set to run at D 18:00 and takes 10 minutes. JOB_20 is set to run at (NOALL,SAT) 18:00 and takes 15 minutes. JOB_10 starts executing on Monday 18:00, with daily executions. On Saturday both JOB_10 and JOB_20 will start executing at 18:00. They will execute in parallell in spite of the dependency between them. Why is this ? ============= It seems that the dependency between JOB_10 and JOB_20 was satisfied already on Monday when JOB_10 executed the first time. The command "SCHED SHOW JOB JOB_20 /FULL" shows this as: Job Dependencies: ([JOB_10]) Solution ? ========== What would be desired is that the dependency between JOB_10 and JOB_20 should always work. Handling the situation via prefunctions is not an acceptable solution since prefunctions are not currently supported on agents. Handling the situation by starting JOB_20 10 minutes after JOB_10 is not an acceptable solution since JOB_10 may be delayed due to heavy CPU load or the like. Handling the situation by "hardcoding" scheduler commands into the jobs JOB_10 and JOB_20 is not acceptable since they might be executed on remote nodes (agents). Assume that JOB_10 executed hourly and JOB_20 daily. The solution should cover this case also. Best regards, and looking forward to your solution. Anders Wallin S-E-B Data, Stockholm ([email protected])
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1104.1 | try DEPENDENCY_TIMEOUT (V3) | HELIX::WARNER | It's only work if they make you do it | Tue May 21 1996 10:56 | 3 |
Have you tried using DEPENDENCY_TIMEOUT (if you're using V3)?
-Ross
| |||||
| 1104.2 | MRBASS::PUISHYS | Project Leader Scheduler V3.0 for Digital UNIX | Thu May 23 1996 09:59 | 30 | |
To handle this exact problem
of a job running on a different day and having it satisfy a dependencies for
the next time both job want to run, (boy thats a mouth full), we have added
into V3.0 a feature called dependency timeout.
It allows you set set a time that the dependency needs to run by to be valid.
ie if the dependecies have not run with in 12 hours don't count them.. Wait
until they run within 12 hours.
Ofcourse this is in V3.0 for UNIX not 2.1
So the best way in 2.1 is to do a is use the scheduler command:
SCHEDULE
SET
JOB
/CLEAR_DEPENDENCY
/CLEAR_DEPENDENCY
Reset the synch time of the specified job to the current time. This
actually clears any dependency requirements that have already been
met so that they must be met again.
I would create a job that only runs late sunday to clear the dependency on job20
and the uses jobs will run ok.
bob
| |||||
| 1104.3 | MRBASS::PUISHYS | Project Leader Scheduler V3.0 for Digital UNIX | Thu May 23 1996 10:00 | 4 | |
Just a note to .1 dependency_timeout has a bug in V3.0 and does not work as described, but will soon | |||||