Archives of the TeradataForum

Message Posted: Thu, 28 May 2009 @ 21:06:57 GMT

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

One thing to watch out for in any of these (including PMON) is that if you are using workload management, rather than the (older) priority schedular itself, the prefix seen in the Account string (and therefore what is displayed by PMON etc.) may not be the priority at which the session is actually executing.

The original 'Priority' field was only 2 characters long so it has not been used for a long time. The displayed priority now comes from the account prefix. Unfortunately when priorities are set via workload management the prefix of the Account field is not changed to match... So the resulting prefix is likely to be wrong.

Mike Dempsey
Teradata Client Tools

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