Timeouts -- forcing one or seeing mc_jobs data for one

[Former Member]

I'm trying make a SQL monitoring job which would report when IDM jobs are in certain bad statuses. Things like fatal Errors are simple -- just check for state = -1 -- but I need to know exactly what's in mc_jobs when a job is in various states of timeout so I can report it accurately.

If anyone knows this offhand, then great! Otherwise, I'd love a method to simulate these timeouts so I can both figure it out myself and test the SQL job. I can hit an Idle Timeout easily by scheduling a job for Every Minute but not giving it a dispatcher, then waiting for that timeout for expire. I'm trying to simulate others by having a job start and then call a script with an infinite loop.

Thanks!

Chris

Edited by: Chris Foley on Feb 23, 2012 2:08 AM

[Former Member]

It was enough to just simulate the single timeout. state = -2 indicates timeout and we didn't need to get any more granular than that.