I have a job that kicks in when it finds a semaphore file, but when it finds it it does not start - it says in the log "Semaphore file found" etc but does not perform the JAL script. Why could this be ?

: I have a job that kicks in when it finds a semaphore file, but when it finds
: it it does not start - it says in the log "Semaphore file found"
: etc but does not perform the JAL script. Why could this be ?
I changed the queue to one different from the default and it now works - why is this ? How can I stop this from happening ? Should I increase the size of my default queue ?

The problem is not in the queue size, but in the queue usage. After 24x7 found the file it submited the job to the assigned queue where the job is still waiting for the start. As soon as as the queue manager will complete all previously queued jobs it will run this job. Every queue has its own queue manager process. When you changed the job queue and rerun the job the other queue manager was free and immediatelly executed it.

: I changed the queue to one different from the default and it now works - why
: is this ? How can I stop this from happening ? Should I increase the size
: of my default queue ?

Additional note: Jobs are inserted into queues according to their priority. If you have jobs with low or normal priority and you also have other jobs with higher priority assigned to the same queue and running frequently, those higher priority jobs keep getting into the queue in front of low priority jobs and not letting them to run.

You should monitor job queues if you want to get an idea how your jobs run. Use different queues for different group of jobs. It is also a good idea to use different queues for frequently running jobs and all other jobs.

: The problem is not in the queue size, but in the queue usage. After 24x7
: found the file it submited the job to the assigned queue where the job is
: still waiting for the start. As soon as as the queue manager will complete
: all previously queued jobs it will run this job. Every queue has its own
: queue manager process. When you changed the job queue and rerun the job
: the other queue manager was free and immediatelly executed it.

thanks for that info - I have a problem with the job monitor - because whenever I use it it freezes up and I have to End Task the scheduler so I can't use it all really.

You can simply monitor files in job queue directories. 1 file matches 1 queued job.

: thanks for that info - I have a problem with the job monitor - because
: whenever I use it it freezes up and I have to End Task the scheduler so I
: can't use it all really.