status of jobs in process when 24x7 service is stopped

We experienced some unusual behavior yesterday with jobs that were supposed to run but did not.

We run 24x7 as a service. To rerun a job manually, the only way we know how is to stop the service, open 24x7 and "run" the script manually.

We have hundreds of jobs that are running during each day and some of them are large Oracle related jobs that take more than an hour to complete. The 24x7 scripts are multi step scripts for each of the different Oracle procedures it calls.

I am concerned that when we stopped the scheduler service yesterday to run a job manually, that any job that was in process did not complete successfully. We do not see "....job finished" for several jobs. Should we be re-running manual jobs a different way?

Also, on the 24x7 job log we saw serveral times yesterday the comment of "24x7 Scheduler terminating...". Where is this message coming from, and does it impact jobs that are in process?

If you run the scheduler in service mode, you should use either the 34x7 Remote Control or 24x7 web-based Management Console to communicate with the scheduler in on-line client/server mode. You don't need to stop it or restart it in order to see jobs, logs, and run and manage jobs as needed.

Also you can always start jobs manually from the command line using "24x7.exe /JOB" command. This way you don't have to stop the service.