Archives of the TeradataForum

Message Posted: Fri, 13 Jun 2014 @ 19:24:49 GMT

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

Checked with a colleague and here is his response:

Looks like the thread already mentions filter-based reject and throttling at zero.

Being an appliance and requiring a schedule of different settings for filters/throttles, I've seen the use of TDWMSetLimits and TDWMApply to change the value of a throttle. These are stored procedures in the tdwm database. An external scheduler is configured to make the necessary calls to these TDWM "open API" stored proc calls.

See the Application Programming Reference manual, Teradata Release 14.10, Chapter 5 Teradata Dynamic Workload Management APIs.

Filters are a bit trickier. I believe you have to rely on the TDWMRuleControl procedure. This updates the EnabledFlag of the rule and the EnabledFlag in the base state for the rule. "Base state" is the catch. The TDWMRuleControl procedure must be used with rules defined only with the base state, as this is the only state value that this procedure changes. This shouldn't be as much of a concern on an appliance pre-TD15, as you don't have the state matrix with appliance workload management (TIWM).

Cautions:

Once a throttle limit is set to a specific value using the TDWMSetLimits stored procedure call , it cannot be set to the "Unlimited" option without using the Workload Designer GUI. Set the throttle value to a very high value to mimic the "Unlimited" option.

Multiple filter and/or system throttle rules can be modified using multiple TDWMSetLimits stored procedure calls. After the TDWMSetLimits calls are made, make just one call to the TDWMApply stored procedure to update the active ruleset. Make sure to specify 'Y' for each TDWMApply parameter representing each TASM/TIWM category that is modified (e.g. filters, throttles, workloads, events).

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