Fixes are available
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 number
IZ71067
Reported component name
TEP
Reported component ID
5724C04EP
Reported release
621
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-25
Closed date
2010-05-04
Last modified date
2010-07-22
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
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621"}]
Document Information
Modified date:
30 December 2022