Start of change

User task and transaction class task system rules

You can use user task and transaction class task system rules to monitor system and transaction class definition (TRANCLASS) task load by specifying a message to be issued or an event to be emitted when the active task count crosses a threshold value.

User task and transaction class task system rule thresholds are expressed as a percentage of the maximum number of active tasks in the system or transaction class (TRANCLASS). For performance reasons, the threshold values you can specify are predefined.

The possible threshold values you can select are 50%, 60%, 70%, 80%, 90%, and 100% of the MXT system initialization parameter or TRANCLASS MAXACTIVE value.
  • You can filter on a threshold to indicate how close the system is to MXT. You can define more than one system rule to indicate various degrees of health as the threshold gets closer to the limit that you set for the MXT system initialization parameter.
  • You can filter on the TRANCLASS and a threshold to indicate how close the TRANCLASS is to its MAXACTIVE value. You can define more than one system rule to indicate various degrees of health as the number of attached tasks gets closer to the MAXACTIVE limit that you set for the TRANCLASS resource.

To avoid large numbers of messages or events being emitted, user task and tranclass task system rules are only evaluated when the number of active tasks crosses a threshold value and has been either above the next higher threshold or below the next lower threshold since last time when rules for that threshold value were evaluated.

For example, any "goes above 60% of MXT" rule is evaluated during transaction attach only when the number of active tasks exceeds 60% of the MXT value and the number of active tasks has either been above 70% of MXT or below the 50% of MXT since the "goes above 60% of MXT" rule was evaluated last time. Figure 1 shows examples to help you understand this algorithm.

Figure 1. Rule actions
An example line graph of the values of number of active tasks over elapsed time. Points on the graph indicate where the number of active tasks crosses a threshold value and triggers rule evaluation.

Rules are evaluated as follows:

 1  No user task or tranclass task rules are evaluated when the number of active tasks exceeds the 50% threshold. Rules are only evaluated during transaction attach when the number of active tasks goes above the 60%, 70%, 80%, 90%, or 100% thresholds, and during transaction detach when the number of active tasks goes below the 50%, 60%, 70%, 80%, or 90% thresholds. No rules are evaluated when the number of active tasks fluctuates around the 50% threshold, because the number of active tasks has not been above the 60% threshold since we last evaluated any "goes below 50%" rules.

 2  Rules are evaluated because the number of active tasks crosses the 60% threshold for the first time since it last crossed the 50% threshold.

 3  Rules are evaluated because the number of active tasks crosses the 70% threshold for the first time since it last crossed the 60% threshold.

 4  No action is performed when the number of active tasks oscillates around the 70% threshold because the number of active tasks does not go above 80% or below 60% in the intervening period of time.

 5 Rules are evaluated because the number of active tasks drops below the 60% threshold for the first time since it last crossed the 70% threshold.

 6  A series of actions are performed when the number of active tasks progressively exceeds the 60%, 70%, 80%, 90%, and 100% thresholds.

Considerations

No transaction class system rules are evaluated for transactions that are defined with a MAXACTIVE value of less than 10 in the TRANCLASS.

No transaction class system rules are evaluated for transactions that do not belong to any TRANCLASS, that is, any transaction defined with TRANCLASS(DFHTCL00).

If you require an event to be emitted when the number of user tasks or transaction class tasks goes above the 100% threshold, and that you need the event to be emitted as quickly as possible, consider the dispatch characteristics of the EP adapter specified by the policy rule:
  • For a user task system rule, ensure that the specified EP adapter will be linked to. An attached EP adapter task might be queued until the MAXTASK condition is cleared.
  • For a transaction class system rule, ensure that the TRANCLASS that causes the event is not used by an attached EP adapter task.


systemrules-tranclass-user.html | Timestamp icon Last updated: Sunday, 4 June 2017
End of change