IV11717: UA SITUATION W/ MISSING FUNCTION MAY PRODUCE A FALSE POSITIVE
Fixes are available
Closed as program error.
Environment: ITM Universal Agent 622FP5 Problem Description: UA Situation w/ MISSING function may produce a false positive. The case for the false positive is when UA has a set of data rows in its cache and said data rows are NOT missing the specific attribute value that MISSING() function is testing for, yet the situation fires anyway. Detailed Recreation Procedure: 1. Install and configure UA 622FP5 on Windows or *nix system. 2. Set up an situation for that UA with MISSING function. 3. Start that situation,you will find it will be fired one time at every startup of this situation, although it doesn't match the fired condition.
Situation with MISSING function may product a false positive. When running a Situation that uses MISSING() function against a Universal Agent application where current, monitored attribute value(s) is/are not missing, the Situation will incorrectly evaluate as true, thus marked as 'open' state. This behavior is most readily observed when stopping and then restarting the Situation at a time when attribute at issue is not missing the value(s) of interest. SPECIAL NOTE: This APAR fix does not prevent a Situation using MISSING() function from false positive in case where there are no data rows present in memory cache for the associated Universal Agent application. This particular scenario will be addressed in a future TEMA release.
Universal Agent data row processing was modified for case of situation that contains MISSING() function so that current data rows of associated Universal Agent application are always sent to the TEMA framework for evaluation by the MISSING() function; this design change eliminates the behavior of false positive Situations that contain MISSING() function. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.2.2-TIV-ITM-FP0008 | fix pack | 6.2.3-TIV-ITM-FP0002
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels