Since the last update 3.4.2(b) the scheduler "says" (last run/nextrun) that a job has run, but none of the logs(text/web/etc) indicate that anything happend. For example, I had a job that was supposed to run @ 2300 last night. I checked it this morning, and the job status said that it had run and the next run was 2300 tonight, but none of the log files or text files that job modified had any datestamps after 17:15, which is when I left the office.

help.

Is this a script type job?
Can the job fail to update the referenced files?

: Since the last update 3.4.2(b) the scheduler "says" (last
: run/nextrun) that a job has run, but none of the logs(text/web/etc)
: indicate that anything happend. For example, I had a job that was supposed
: to run @ 2300 last night. I checked it this morning, and the job status
: said that it had run and the next run was 2300 tonight, but none of the
: log files or text files that job modified had any datestamps after 17:15,
: which is when I left the office.

: help.

: Is this a script type job?
: Can the job fail to update the referenced files?

Yes it is a script. I suppose it could, but there should be something in the log somewhere...
when jobs run it generates the html log, this does not happen.

If you have tracing enabled check the appropriate [job id].log file in the Performance Data directory. In this file you can find what went wrong.
If you don't have it enabled either run the job in the debugger or tunr on the tracing and run it again. See the log file.

If you find anything unexpected please let us know.

: Yes it is a script. I suppose it could, but there should be something in the
: log somewhere...
: when jobs run it generates the html log, this does not happen.

: If you have tracing enabled check the appropriate [job id].log file in the
: Performance Data directory. In this file you can find what went wrong.
: If you don't have it enabled either run the job in the debugger or tunr on
: the tracing and run it again. See the log file.

: If you find anything unexpected please let us know.
I have tracing enabled. the .log file says that the last time it ran was on 2/17/02

: If you have tracing enabled check the appropriate [job id].log file in the
: Performance Data directory. In this file you can find what went wrong.
: If you don't have it enabled either run the job in the debugger or tunr on
: the tracing and run it again. See the log file.

: If you find anything unexpected please let us know.
Except for 6:30 today when I ran it manually.

Do you have 2 jobs with the same name by any chance?
Are you sure the log shows "job started" message for this job and

: I have tracing enabled. the .log file says that the last time it ran was on
: 2/17/02

: Do you have 2 jobs with the same name by any chance?
: Are you sure the log shows "job started" message for this job and

I tried to close 24x7 and there was 1 "spawned process" that was outstanding. How was I to detect this ? Restarting seems to have remedied the situation.

You can use the Queue Monitor to check what jobs are running.

: I tried to close 24x7 and there was 1 "spawned process" that was
: outstanding. How was I to detect this ? Restarting seems to have remedied
: the situation.