Triggering using Semaphores

Dear Support,

I have recently purchased the Scheduler and have been running several batch jobs using semaphore triggering. I have noticed that sometimes, my programs do not get triggered even though the *.dat has been saved and the triggering has worked successfully many times before.

When the jobs do not get triggered even though their trigger job has begun and completed, I will stop the scheduler and run the job again later. Eventually, the batch will run normally again.

However, I believe that this is not the expected behaviour of a scheduled job. Would you have any suggestions as to why this is happening? And what can I do to overcome this problem?

Rachel

Are your *.dat files stored on a network drive?
Do programs that create these *.dat files properly release them?
When you say, restart the scheduler, do you restart the computer?

: Dear Support,

: I have recently purchased the Scheduler and have been running several batch
: jobs using semaphore triggering. I have noticed that sometimes, my
: programs do not get triggered even though the *.dat has been saved and the
: triggering has worked successfully many times before.

: When the jobs do not get triggered even though their trigger job has begun
: and completed, I will stop the scheduler and run the job again later.
: Eventually, the batch will run normally again.

: However, I believe that this is not the expected behaviour of a scheduled
: job. Would you have any suggestions as to why this is happening? And what
: can I do to overcome this problem?

: Rachel

: Are your *.dat files stored on a network drive?
: Do programs that create these *.dat files properly release them?
: When you say, restart the scheduler, do you restart the computer?

No, the *.dat files are not stored on a network drive but on a single computer.

I believe the program that starts off the first trigger job (which creates all the semaphores) does release the *.dat files properly because a check for the semaphore files on the hard disk reveals that all semaphore files were created and the option to check for semaphore files every x minutes has not been unchecked. The other jobs just do not get triggered.

The computer is not restarted. The scheduler job is deleted from the Windows Task Manager before running the scheduler again.

Have you tried upgrading to the most recent version 2.3.5 that fixes some problems with lost handles?

: No, the *.dat files are not stored on a network drive but on a single
: computer.

: I believe the program that starts off the first trigger job (which creates
: all the semaphores) does release the *.dat files properly because a check
: for the semaphore files on the hard disk reveals that all semaphore files
: were created and the option to check for semaphore files every x minutes
: has not been unchecked. The other jobs just do not get triggered.

: The computer is not restarted. The scheduler job is deleted from the Windows
: Task Manager before running the scheduler again.

: Have you tried upgrading to the most recent version 2.3.5 that fixes some
: problems with lost handles?

Ooh, I didn't know that but I will download the latest version and try it out.

Could I just have a quick check with you? Currently my JAL script has been written to disable jobs that have errors in execution. Hence, if I were to run the batch again, let's say the next day, my JAL script will read all from a file all the existing jobs and enable all jobs.

Using version 2.3.2, I have discovered that disabled jobs are enabled once more but the other jobs, which normally get triggered and work fine, do not run. The semaphore files are created but nothing else happens. Was this problem reported before and does the new version fix this particular handling problem?

Anyway, I do hope you can reply to this question. I have finished downloading the upgrade and will try it out now.

Hello there again,

I've tested the latest version 2.3.5 and the same problem still occurs. I've checked my directories and the semaphore files are not created hence the other jobs are not being triggered. But this shouldn't be happenning....

Here is the bit of code I am using:

IniFileGetKey("C:\Batch\24x7 Scheduler\Config\24x7settings.ini", "Batch Jobs", "jobnames", batchjob)
//Reset all DISABLED Jobs
FileOpen(batchjob, "LineMode", "Read", "", file_number)
EOF(file_number, end_of_file)

LoopUntil end_of_file Finish
FileRead(file_number, jobname)
JobModify(jobname, "DISABLED", "N")
EOF(file_number, end_of_file)
Finish:
FileClose(file_number)

//Then proceed to run the trigger job

With the code, only if I step through the program will the semaphore files be created and the rest of the jobs triggered.

Without the enabling bit of code, the trigger job works okay and all the semaphore files are created.

Is there anything else I can do? I would like the enabling of jobs within the same script as the trigger.

Thank you!!!

: Ooh, I didn't know that but I will download the latest version and try it
: out.

: Could I just have a quick check with you? Currently my JAL script has been
: written to disable jobs that have errors in execution. Hence, if I were to
: run the batch again, let's say the next day, my JAL script will read all
: from a file all the existing jobs and enable all jobs.

: Using version 2.3.2, I have discovered that disabled jobs are enabled once
: more but the other jobs, which normally get triggered and work fine, do
: not run. The semaphore files are created but nothing else happens. Was
: this problem reported before and does the new version fix this particular
: handling problem?

: Anyway, I do hope you can reply to this question. I have finished downloading
: the upgrade and will try it out now.

Hi there! I've noticed something really odd. When I tried to just enable one job, all the semaphores to be created by that particular job was created. I tried it with two jobs and the last job's semaphores were created.

So to overcome my problem of semaphores not being created, I have put my trigger job as the last job to be enabled. Everything is running as expected now.

Thanks for everything!

: Hello there again,

: I've tested the latest version 2.3.5 and the same problem still occurs. I've
: checked my directories and the semaphore files are not created hence the
: other jobs are not being triggered. But this shouldn't be happenning....

: Here is the bit of code I am using: IniFileGetKey("C:\Batch\24x7
: Scheduler\Config\24x7settings.ini", "Batch Jobs",
: "jobnames", batchjob)
: //Reset all DISABLED Jobs
: FileOpen(batchjob, "LineMode", "Read", "",
: file_number)
: EOF(file_number, end_of_file)

: LoopUntil end_of_file Finish
: FileRead(file_number, jobname)
: JobModify(jobname, "DISABLED", "N")
: EOF(file_number, end_of_file)
: Finish: FileClose(file_number)

: //Then proceed to run the trigger job

: With the code, only if I step through the program will the semaphore files be
: created and the rest of the jobs triggered.

: Without the enabling bit of code, the trigger job works okay and all the
: semaphore files are created.

: Is there anything else I can do? I would like the enabling of jobs within the
: same script as the trigger.

: Thank you!!!

What do you mean by "disabled jobs are enabled once more"?

PS. disabled jobs do not check for semaphore files, but can create some if they are forcibly ran from other jobs using JobRun statement