I have a job that is scheduled to run at 7am, but it doesn't start.
When I look at what other jobs are running I hav eanother job that is running also. This other job is usually WAITing for 600 (ie ten mins) as it is looking for a file and if it doesn;t exist it waits ten mins then checks again. The job I want to run also does this, but the file DID exist for the job I want to run so when I clicked on RUN NOW it ran straight away. I am sure it is because this other job is set to WAIT that is stopping it from running. Both jobs are set to Asynchronous.

Any ideas ?

: I have a job that is scheduled to run at 7am, but it doesn't start.
: When I look at what other jobs are running I hav eanother job that is running
: also. This other job is usually WAITing for 600 (ie ten mins) as it is
: looking for a file and if it doesn;t exist it waits ten mins then checks
: again. The job I want to run also does this, but the file DID exist for
: the job I want to run so when I clicked on RUN NOW it ran straight away. I
: am sure it is because this other job is set to WAIT that is stopping it
: from running. Both jobs are set to Asynchronous.

: Any ideas ?
another job has not run either !! None of these jobs are disabled. I have had to run them manually - why is this happening ?

Check the job queue, you should see those jobs waiting in the queue.

There are two ways to separate long running jobs:
Put them in a separate job queue so they don't hold other jobs in the may queue or set them to run asynhronous so they can run in the background again do not holding other jobs.

: another job has not run either !! None of these jobs are disabled. I have had
: to run them manually - why is this happening ?