IV65376: FILE TREND SITUATION DOES NOT FIRE IF THE MONITORED FILE GETS DELETED

IBM Tivoli Monitoring 6.3.0 Fix Pack 5 (6.3.0-TIV-ITM-FP0005)

APAR status

• Closed as program error.

Error description

• Problem:
  When the file being monitored by a situation on the Windows OS
  agent File Trend attribute group no longer exists no rows of
  data are sent to TEMA/TEMS. The situation keeps running but
  with no effects until the file gets created again. This is the
  designed behavior for this kind of monitoring but breaks
  customers who wish to be alerted also on the condition that the
  file does not exist.
  
  An ad-hoc environment variable will be introduced by this APAR
  to enable sending a data row with all undefined values for a
  non existing file.
  Default behavior will not change.
  
  Affected Platforms / Versions: Windows OS Agent 6.30 FP2 or
  later
  
  Diagnostics: N/A
  
  Initial Impact:
  Low: monitoring deletion of files should be performed using the
  File Change attribute group
  
  Additional Keywords:
  NTFLTREND
  NT_FILE_TREND
  

Local fix

Problem summary

• Situation on File Trend attribute group does not trigger if the
  file gets deleted.
  
  Situation on File Trend attribute group does not trigger if the
  file gets deleted. Assume you are running a situation based on
  Date Time Last Modified attribute to be alerted whenever a
  change occurs to the file. After the file is deleted the
  situation will not trigger because no rows are sent any longer.
  In order for this APAR to be properly implemented in your
  environment, a new environment variable has been added. See the
  "Install Actions" section of the APAR conclusion for more
  details.
  

Problem conclusion

• Introduced new environment variable that allows to keep sending
  a row of data for a missing file.  Attributes that cannot be
  collected will be reported as Undefined. Default behavior is
  unchanged.
  
  Install Actions:
  set NT_FILETREND_MUST_EXIST=0
  allowed values 0|1, 1 is the default
  
  The fix for this APAR will be contained in the following
  maintenance packages:
  
  | FixPack    | 6.3.0-TIV-ITM-FP0005
  

Temporary fix

• Depending on the actual conditions to be monitored you may
  switch using the File Change attribute group.
  

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

  ITM AGENT WINDO

• Fixed component ID

  5724C040W

Applicable component levels

• R630 PSY

     UP

• R610 PSN

     UP

• R620 PSN

     UP

• R621 PSN

     UP

• R622 PSN

     UP

• R623 PSN

     UP