Pending instance thresholds

The Pending Instance Thresholds setting enables a listener to pause or resume for a specific watch. This setting allows high and low initialization-pending maps for any given watch to turn listeners on or off for that particular watch only.

The use of this setting can improve performance by enabling watches to run that could not run previously because of other watches monopolizing system resources.

If two watches share the same event (what an adapter is triggering), the two watches must have the same values for high and low pending instance thresholds. Otherwise, an error occurs, preventing the Launcher from starting.

During initialization, properties of the watch, including high and low parameters, are written to the debug trace (.txt) file (see Trace and Log Files Naming Conventions for the specific naming conventions).

Note: The global InitPendingHigh and InitPendingLow settings in dtx.ini regulate all listeners and events. The Pending Instance Thresholds Launcher setting regulates listeners for a specific watch (or watches) based on individual watch settings for high and low pending maps. If the InitPendingHigh and InitPendingLow settings in the Launcher section of the dtx.ini file are also set, the Pending Instance Thresholds Launcher settings will take precedence.

Setting: Description
Hi: Value (no limit) for the watch to pause the event or events for that watch. The default value is 0.
Low: Value (no limit) for the watch to resume the event or events for that watch. The default value is 0.