If you are a TASM user, there is an option that springs up when you create a workload, labeled Enforcement Priority. The option name sounds a little more intimidating than it actually is. I’d like to take this opportunity to explain what enforcement priority is, what it actually does, and what it doesn’t do, and just how seriously you should take it.
There are four enforcement priorities, and every workload you define must be assigned one of those four. Enforcement priority doesn’t have anything to do with how resources are allocated, neither does it provide a priority boost to the more important work, at least not directly (I’ll explain what I mean by “not directly” a little further down). Rather, it is a way of for you to characterize and label the relative importance of the work running in that workload.
The four enforcement priorities to choose from include:
In Viewpoint Workload Designer, select the General tab under Workload and you can see where to establish enforcement priority for a workload.
For the most part, enforcement priorities are passive. They are a method of grouping workloads with similar importance. Viewpoint uses enforcement priority to group and report on workloads, for example. However, there are a couple of ways in which they play an active role:
Enforcement priority was so named because at the time of the first TASM release enforcement priority was intended to be used in some future release to play an active part in influencing access to resources. However, with the emergence of Linux SLES 11 and a new priority scheduler for the Teradata Database, enforcement priority has been replaced by some of the new features and capabilities that SLES 11 offers.
So today, think of enforcement priority as primarily documentation, a method of grouping similar workloads for reporting and viewing purposes, with Tactical being the only case of any active, performance-related benefit. In fact many Teradata TASM users simply use the default enforcement priority of Normal for all their non-tactical workloads, so they can more easily move them between allocation groups, as tuning necessitates.
One thing I want to add, before I forget it. When you migrate from Linux SLES 10 to SLES 11, enforcement priority will play a small role in the automatic migration that takes place from the old priority setup to the new priority setup. Once again, this only applies to Tactical workloads. Any workload with a Tactical enforcement priority in SLES 11 will automatically be given a special very high priority positioning within the SLES 11 world.
So the bottom line on enforcement priority is that as long as you get your tactical workloads labeled correctly, it is not going to impact your performance or the balance of your work no matter which enforcement priorities you assign to the other workloads. However, you may find some benefit in the grouping that is done using enforcement priorities when it comes to viewing or filtering your workloads in Viewpoint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.