Task thresholds are expressed as a percentage of the maximum number of active tasks in the system or TRANCLASS. For performance reasons, they 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 event to indicate various degrees of health as the threshold gets closer to the limit 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 event to indicate various degrees of health as the number of attached tasks gets closer to the MAXACTIVE limit you set for the TRANCLASS resource.
To avoid large numbers of events being emitted, events are emitted only when the number of active tasks crosses a new threshold boundary. For example, events are emitted during transaction attach when the number of active tasks exceeds a threshold after being less than the previous lower threshold; and during transaction detach the first time it goes less than a threshold after exceeding the previous greater threshold, as shown in Figure 1.
1 No events are emitted when the number of active tasks exceeds the 50% threshold, events are only emitted during transaction attach when the number of active tasks crosses either of the 60, 70, 80, 90, or 100% thresholds. No events are emitted when the number of active tasks goes less than the 50% threshold as the number of active tasks has not previously exceeded the 60% threshold.
2 An event is emitted because the number of active tasks has been less than the 50% threshold since the last time the number of active tasks exceeded the 60% threshold.
3 An event is emitted because the number of active tasks has been less than the 60% threshold since the last time the number of active tasks exceeded the 70% threshold.
4 No events are emitted when the number of active tasks oscillates around the 70% threshold as the number of active tasks have not exceeded the 80% threshold since the last time the number of active tasks exceeded the 70% threshold, or the number of active tasks have not been less than the 60% threshold since the last time the number of active tasks were less than the 70% threshold.
5 An event is emitted because the number of active tasks has exceeded the 70% threshold since the last time the number of active tasks was less than the 60% threshold.
6 A series of events are emitted as the number of active tasks exceeds the 60%, 70%, 80%, 90%, and 100% thresholds.
Event emission is not enabled for a TRANCLASS when its MAXACTIVE is set to less than 10.
TRANCLASS threshold events are not emitted for those transactions defined as not having a TRANCLASS, that is, those defined with TRANCLASS(DFHTCL00).