We have external job, which should create semaphore file
when it finished. It works perfectly in case when this
job is scheduled for some time (I mean if it should start
at 13.30 and it takes 5 minutes to run this job, semaphore file
would be created at 13.35), but when we run this job from command line
(as 24X7.EXE /JOB jobid) it finishes in seconds not waiting for external
job to be finished and creates semaphore file immediately.
For us is really important to run job from command line and have semaphore file
only when the external job is really finishes, is it possible?

Thanks,

Eugene

The job should run exactly the same in both modes. What does it do? Why does it finish much faster from command line? Any related errors or warning reported in the job log?

: We have external job, which should create semaphore file
: when it finished. It works perfectly in case when this
: job is scheduled for some time (I mean if it should start
: at 13.30 and it takes 5 minutes to run this job, semaphore file
: would be created at 13.35), but when we run this job from command line
: (as 24X7.EXE /JOB jobid) it finishes in seconds not waiting for external
: job to be finished and creates semaphore file immediately.
: For us is really important to run job from command line and have semaphore
: file
: only when the external job is really finishes, is it possible?

: Thanks,

: Eugene