IZ74698: TACMD LISTSIT -M <MANAGED SYSTEM> DOES NOT WORK WHEN HISTORICAL COLLECTION IS ENABLED ON THE MANAGED SYSTEM

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

• Approver:LG
  
  Environment: Windows and zLinux at ITM 622 FP1.
  
  Problem Description:
  
  recreate steps
  1) have OS agent (LZ in our case) at 06.22.01.00 level connected
  and some regular situations deployed to it and started
  
  2) verify with "tacmd listsit -m hostname:LZ"  that situations
  started on it
  
  3) create MSL (lets say HIST_LZ_CUSTOM) and add that agent to
  that MSL
  
  4) configure historical collection (lets say for Linux Process)
  and distribute it to HIST_LZ_CUSTOM MSL instead of RTEMS
  (Distribution tab of history configuration item -> "Managed
  System(Agent) radio   button->add HIST_LZ_CUSTOM MSL to "Start
  collection on")
  
  5) try "tacmd listsit -m hostname:LZ"   again and watch it
  return no output at all
  
  
  6) tacmd also fails if historical configuration is to an
  individual managed system as well as through a MSL.
  

Local fix

Problem summary

• The 'tacmd listsit -m <MANAGED SYSTEM>' command does not
  work when historical collection is enabled on the managed
  system.
  

Problem conclusion

• The logic for the listsit option has been changed to properly
  allow the check on historical data collection.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-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

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R622 PSY

     UP