my job runs and it set to produce a semaphore file but doesn't - as a result the job that depends on this semaphore never runs - why is this please ?

There are could be 3 reasons:
1. the semaphore file is created in another directory (is the file path specified?)
2. the job does not complete and hangs or just fails
3. the finish notification event is not checked

: my job runs and it set to produce a semaphore file but doesn't - as a result
: the job that depends on this semaphore never runs - why is this please ?

: There are could be 3 reasons: 1. the semaphore file is created in another
: directory (is the file path specified?)
: 2. the job does not complete and hangs or just fails
: 3. the finish notification event is not checked

I am not defining a path - I leave it to default to 24x7 as it works for other jobs, I will try defining a path.

The job does not seem to finish correctly - there are no error messages but I set the "delete sempahore" to "after run" and it is still there which suggests the jobs is still running for some reason but when I look at the logs they say it has finished - I don't know what to do now, I could rewrite it all in JAL but really it would be nice if it worked automatically.

if I run the job manually doing "Run No" and as long as the semaphore file is there is works fine, why is this ?? Is my job database corrupt ???

Run Now causes the job to run in foreground and out of queue regardless of the asynchronous/synchronous job settings. Check if this setting somehow affects the semaphore file related job behavior.

Did the addition of file path change anything?

: if I run the job manually doing "Run No" and as long as the
: semaphore file is there is works fine, why is this ?? Is my job database
: corrupt ???

: Run Now causes the job to run in foreground and out of queue regardless of
: the asynchronous/synchronous job settings. Check if this setting somehow
: affects the semaphore file related job behavior.
no the path did not change anything.
The job is running on a remote agent.
I tell it to produce the file d:\semaphores\file.txt where d:\ is on the LOCAL server which is running the master scheduler - is it OK to do this ? It works OK when I invoke Run Now. What setting are you talking about exactly (above) ?
I have told it to run asynchronous and hidden and also have detached checked.

: no the path did not change anything.
: The job is running on a remote agent.
: I tell it to produce the file d:\semaphores\file.txt where d:\ is on the
: LOCAL server which is running the master scheduler - is it OK to do this ?
: It works OK when I invoke Run Now. What setting are you talking about
: exactly (above) ?
: I have told it to run asynchronous and hidden and also have detached checked.
I now switch off asynchronous and detached and it works - I don't want the server to hang tho - that is why I originally switched on asynchronous

Click the "refresh" button to refresh job log view. Are there any errors or warnings.

Does the log for the job look like the following:
1. Found semaphore file...
2. Job started...
3. Agent ... contacted
4. Remote job finished...

IMPORTANT: what's in the record 4? Remote job finished or Remote job posted for execution?

: no the path did not change anything.
: The job is running on a remote agent.
: I tell it to produce the file d:\semaphores\file.txt where d:\ is on the
: LOCAL server which is running the master scheduler - is it OK to do this ?
: It works OK when I invoke Run Now. What setting are you talking about
: exactly (above) ?
: I have told it to run asynchronous and hidden and also have detached checked.

Create a separate job queue and put that job into it. It will have the same effect as running asynhronously however the job itself will run synhronously and everything should work as expected. You can still run it detached.

: I now switch off asynchronous and detached and it works - I don't want the
: server to hang tho - that is why I originally switched on asynchronous

: Create a separate job queue and put that job into it. It will have the same
: effect as running asynhronously however the job itself will run
: synhronously and everything should work as expected. You can still run it
: detached.
I created a new queue and run the job and I still cannot navigate thru the scheduler until the job finishes

Set job priority to Low in order to prevent if from consuming too much CPU processing.

Don't run the job manually. Manually triggered jobs by default run in the foreground.

: I created a new queue and run the job and I still cannot navigate thru the
: scheduler until the job finishes