In an earlier forum thread, it was mentioned that to have the Monitor show the actual Finish Time and Duration Time, the job need to run synchronously and not asynchronously. I am still very new to this and using an Eval copy of the software, but I see no where to set a job to be synchronous, only a check box to make it asynchronous. Is it then by default, synchronous if I do not check the asynchronous box? Without checking the asynchronous box, the Monitor shows that the Start Time and the Finish Time are the same and that the Duration Time is "0", even all though it does take the job several minutes to complete. I am running a simple Python script that has no interactive requierments or dependencies.

Thanks,
Don

What finish time do you get in the job log for that job?

PS. Yes the, the asynchronous box controls job run time mode. Yet, there could be some quirks. For example, from 24x7 you launch process A and set the job to wait for process A completion (run synchronous mode for the job queue). If then from process A you launch child process B and don't wait for B to complete before returning control back to the scheduler it will appear as if the job completes before B is done. In the job log you will see end of A as end of job.

: In an earlier forum thread, it was mentioned that to have the Monitor show
: the actual Finish Time and Duration Time, the job need to run
: synchronously and not asynchronously. I am still very new to this and
: using an Eval copy of the software, but I see no where to set a job to be
: synchronous, only a check box to make it asynchronous. Is it then by
: default, synchronous if I do not check the asynchronous box? Without
: checking the asynchronous box, the Monitor shows that the Start Time and
: the Finish Time are the same and that the Duration Time is "0",
: even all though it does take the job several minutes to complete. I am
: running a simple Python script that has no interactive requierments or
: dependencies.

: Thanks,
: Don

The Start Time is 10:15 AM, the job starts at the correct time, the Monitor shows that the process is running and in about 3 minutes the Monitor shows that the job has completed and the Finish Time is 10:15 AM (same as the Start Time) and the Duration Time is "0". The output file has a timestamp on it of 10:18 AM. There are no separate child processes started during the execution of the job. The job is mostly text string parsing of about 40,000 records and there is a lot of file system I/O.

Thanks,
Don

: What finish time do you get in the job log for that job?

: PS. Yes the, the asynchronous box controls job run time mode. Yet, there
: could be some quirks. For example, from 24x7 you launch process A and set
: the job to wait for process A completion (run synchronous mode for the job
: queue). If then from process A you launch child process B and don't wait
: for B to complete before returning control back to the scheduler it will
: appear as if the job completes before B is done. In the job log you will
: see end of A as end of job.

What about the job log? What do you see in the job log as job completion time? You can see in several places, for example, Tools/Log Vieer menu or on the job log page.

: The Start Time is 10:15 AM, the job starts at the correct time, the Monitor
: shows that the process is running and in about 3 minutes the Monitor shows
: that the job has completed and the Finish Time is 10:15 AM (same as the
: Start Time) and the Duration Time is "0". The output file has a
: timestamp on it of 10:18 AM. There are no separate child processes started
: during the execution of the job. The job is mostly text string parsing of
: about 40,000 records and there is a lot of file system I/O.

: Thanks,
: Don

The job log appears to have the correct start and finish times.

Don

: What about the job log? What do you see in the job log as job completion
: time? You can see in several places, for example, Tools/Log Vieer menu or
: on the job log page.

This means the Job Monitor is unable to find the associated system process id in the task list. In other words when 24x7 starts your process it obtains the system process id (the one you see in the task list) and then it passes that value to the monitor. The monitor periodically checks with the system if the process id is valid and belongs to a running process. If it is not, the monitor assumes that the process has completed and captures that moment as the finish time. Unfortunately there is no way to see which process id it is monitoring so you cannot correlate it with the Windows Task Manager and check if the process id somehow changes.

I suggest that instead of the Job Monitor (which is really a “best guess”) you use either the Queue Monitor or the Log Viewer tool, both of which are updated in a real-time and provide more accurate information as compared to the Job Monitor.

: The job log appears to have the correct start and finish times.

: Don