IZ71067: 'NULL' VALUE TRIPS THRESHOLD ON THE CLIENT

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• When a 'NULL' value is received for an integer column, the TEP
  client incorrectly interprets that value for thresholding.
  
  If the data in the column should be an integer, the 'NULL'
  string value should not be used to set a threshold.
  

Local fix

Problem summary

• Database columns may contain null values if the columns are
  added after records have already been written.  This typically
  happens for historical tables that track data across product
  upgrades that introduce new columns.  The historical records
  written before the upgrade will have null values for any added
  columns.  If a 'greater than' threshold is specified for the
  column, the null values will be incorrectly flagged.
  

Problem conclusion

• The logic was changed to recognize and handle the special null
  values received from the database that indicate the absence of
  data.  The values are treated as not greater than, less than, or
  equal to actual data values.  If both values being compared are
  null then the result will be equal.  This change allows both
  filters and thresholds to work correctly.
  
  The fix for this APAR is included in the following maintenance
  vehicle:
      | fix pack | 6.2.1-TIV-ITM-FP0003
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TEP

• Fixed component ID

  5724C04EP

Applicable component levels

• R621 PSY

     UP