Option 1 is to delete or rename "input" semaphore file so the job B will not find it again and B will not start anymore. Option 2 is to make job B of "script" type and call JobDisable at the end of the run to disable itself. Option 3 is to make job B having "[no schedule]", because job C is watching for the file anyway. Job C of "script" type checks some "semaphore" (to see if the job B ran already, and if not) it kicks off job B using JobRun. For the "semaphore" it can use some other file that it creates before running B and then checks if that file exists. If it is exists, job C does not run B again.
Another good "semaphore" type can be a key in .INI file or Registry (check out templates form the "Monitors" section. They all use .INI files for the "semaphores" : I have some processes running based on dependencies.
: I have process A as a precondition for process B and also process C. : So, both process B and C are dependant on process A. : Process (A) - > Process (B) : - > Process (C). : I've used the Wizard to do the setup and I've specified one minute as the
: frequency to which process B would check for a semaphore created by
: Process (A). The problem is, even after Process (B) is run once, it would
: still continue to keep on running after every minute.... Is there a way to
: specify that we want to run a process JUST ONCE. : It seems that if we choose option - check for existance of semaphore, we
: can't choose option , because the pull down menu allows us to choose only
: one option. : So, my question is: how do we configure process (B) so that it will and at
: the same time, enable process (B) to ? : Can anybody help? Thanks... : Ivan.
|
