stretchoo7
11th September 2008, 23:05
Baan IVc4/Win2k/SQL2K

My Job Daemon will occasionaly (about once every 3-4 weeks) hang with the Windows service showing Started. Dows anyone have any thoughts on the simplest and laziest (in other words, most efficient) way to detect this?

I was thinking of creating something like this:
1. Create Baan job to write a text file hourly
2. Have a Windows scheduled task batch file check for the existence, delete it if it's there, alert me if it's not
3. Do it all over again every hour.

Is there some other way to detect Job Daemon failures when the service shows Started?

Darren Phillips
18th September 2008, 00:52
on all my daily jobs I add a shell command to the baan job that calls blat (a free command line email program) I then get an email saying job1 has completed etc. If I don't get the email at the expected time I know something is wrong.

Neal Matthews
19th September 2008, 15:52
"1. Create Baan job to write a text file hourly
2. Have a Windows scheduled task batch file check for the existence, delete it if it's there, alert me if it's not
3. Do it all over again every hour. "

I do exactly the same thing on UNIX. Cannot really think of any alternative methods.