Archives of the TeradataForum

Message Posted: Wed, 13 Aug 2003 @ 17:18:59 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Wednesday, August 13, 2003 12:39 -->

What Thomas and Carrie have not addressed was the thread ('Re: Priority Scheduler') about xschmon and schmon having a lock conflict. What does NCR say about that?

I have the priority scheduler set up so that each night I change the way some of my groups are set up to run. I have noticed that on a few occasions, the schmon -a command runs (via cron) but the prioritization doesn't change. Has anyone experienced this before?

For example this is one typical entry in my crontab.

45 7 * * 1-5 /usr/ntos/bin/schmon -a 10 N ABS 20 > /dev/null 2>&1
0 19 * * 1-5 /usr/ntos/bin/schmon -a 10 N DEF 10> /dev/null 2>&1

If I enter schmon -d at 19:05, I will see that the priority will be changed. But a handful of times, I have found that it hasn't changed but the cron log says the command was executed.

Thanks

	<Prev	Next>		<<First	<Prev	Next>	Last>>