I assume that this applies to W2000 also.
Does this mean I have to stop the service, invoke the job monitor, schedule
my job(s), then restart the service..in order not to lose already forecasted
jobs?

In Response To: Job Monitor and NT4 service (Graham Laidler)

The Job Monitor attempts to forecast and track down job progress. When the job job database is saved the entire active job pool gets reloaded and the Job Monitor looses track of already forecasted jobs (inserted into the Monitor)

The Job Monitor tracks jobs only in the currently running instance of the 24x7 job engine. If you have 24x7 service running (which is another instance of 24x7 job engine) in background you cannot use the Job Monitor another instance of 25x7 to watch for jobs in the service instance. Think of this if you have 2 Notepad instances open, you cannot use one of them to edit text in another instance.

: Hi,

: Have installed 24x7, and am using it to run several jobs.. a couple of
: strange things happen, just wondering if you could shed some light?

: First, when we save the job definition file, it the job monitor tends to fill
: up with random jobs that are scheduled at various times during the day.
: Next to these is a question mark, rather than the OK symbol. None of these
: jobs have fired.

: Secondly, when running 24x7 as an NT service, none of the scheduled jobs
: appear in the job monitor, and it doesn't run any of them.

: Any help would be appreciated.

: Graham

Yes, it does apply to W2000.

Stop the service. Start GUI and open the Job Monitor, print it, close GUI and start the service.

Again, the GUI is not a pure GUI console for the service. Running GUI while the service is running is like running 2 separate applications. One is the service and another is the GUI (like 2 instances of the Notepad). When you make changes in the GUI instance, it checks if the service is still running and restarts the service so the service instance can reload job database and pick up new changes. This logic is very straight and simple.

The Job Monitor in the GUI does not have (and cannot have) access to the memory of another instance and cannot track jobs running by that service instance. Since the GUI instance does not run jobs while the service is running in background, it has the job engine turned off and so the Job Monitor is unable to track and forecast jobs.

The good news is that in the next version of 24x7 we will have a number of reports that can be used for job tracking and forecasting. These reports will work in any instance.

: I assume that this applies to W2000 also.
: Does this mean I have to stop the service, invoke the job monitor, schedule
: my job(s), then restart the service..in order not to lose already forecasted
: jobs?

: In Response To: Job Monitor and NT4 service (Graham Laidler)

: The Job Monitor attempts to forecast and track down job progress. When the
: job job database is saved the entire active job pool gets reloaded and the
: Job Monitor looses track of already forecasted jobs (inserted into the
: Monitor)

: The Job Monitor tracks jobs only in the currently running instance of the
: 24x7 job engine. If you have 24x7 service running (which is another
: instance of 24x7 job engine) in background you cannot use the Job Monitor
: another instance of 25x7 to watch for jobs in the service instance. Think
: of this if you have 2 Notepad instances open, you cannot use one of them
: to edit text in another instance.

When I stop an error message indicating that the service could not be stopped,
but it really is with an Error 997: Overlapped i/o operation in progress.

Should the above message be ignored?

: Yes, it does apply to W2000.

: Stop the service. Start GUI and open the Job Monitor, print it, close GUI and
: start the service.

: Again, the GUI is not a pure GUI console for the service. Running GUI while
: the service is running is like running 2 separate applications. One is the
: service and another is the GUI (like 2 instances of the Notepad). When you
: make changes in the GUI instance, it checks if the service is still
: running and restarts the service so the service instance can reload job
: database and pick up new changes. This logic is very straight and simple.

: The Job Monitor in the GUI does not have (and cannot have) access to the
: memory of another instance and cannot track jobs running by that service
: instance. Since the GUI instance does not run jobs while the service is
: running in background, it has the job engine turned off and so the Job
: Monitor is unable to track and forecast jobs.

: The good news is that in the next version of 24x7 we will have a number of
: reports that can be used for job tracking and forecasting. These reports
: will work in any instance.

This message appears on W2K only and should be ignored. In two words, it means that W2K found out that the service being stopped is busy doing something. And it really is. The 24x7 service control manager is stopping the 24x7 job engine which is running as a separate process.

: When I stop an error message indicating that the service could not be
: stopped,
: but it really is with an Error 997: Overlapped i/o operation in progress.

: Should the above message be ignored?