Hello all,
Having had a major disk issue over the weekend (the engineers are still downstairs puzzling over the RAID), I'm reconsidering the route taken with Scheduler when the database is down.
At present, the first script to run checks the connection to the database and if there's a problem, it emails me and goes into an infinite loop to prevent the remaining scripts from running. Not very elegant and I'm concerned that it may use processor time (the same server also hosts the cubes in Upfront). I guess I could change it so that it looped for x hours so as to filibuster the subsequent scripts on the 'run x hours after' setting of Scheduler.
Is there a command I can use within a script or a bat file I can shell out to that will terminate Jobmgr32.exe and/or schdl_go.exe?
Many thanks,
lex
soi la, soi carré
Having had a major disk issue over the weekend (the engineers are still downstairs puzzling over the RAID), I'm reconsidering the route taken with Scheduler when the database is down.
At present, the first script to run checks the connection to the database and if there's a problem, it emails me and goes into an infinite loop to prevent the remaining scripts from running. Not very elegant and I'm concerned that it may use processor time (the same server also hosts the cubes in Upfront). I guess I could change it so that it looped for x hours so as to filibuster the subsequent scripts on the 'run x hours after' setting of Scheduler.
Is there a command I can use within a script or a bat file I can shell out to that will terminate Jobmgr32.exe and/or schdl_go.exe?
Many thanks,
lex
soi la, soi carré