IV07902: AUTOMATED CLEARDEPLOYSTATUS PROCESSING NEEDED

IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)
IBM Tivoli Monitoring 6.2.3 Fix Pack 2 (6.2.3-TIV-ITM-FP0002)
IBM Tivoli Monitoring 6.2.3 Fix Pack 4 (6.2.3-TIV-ITM-FP0004)

APAR status

• Closed as program error.

Error description

• In moderate and larger size (10,000+ endpoint) enterprise
  environments there is a need to age out deploy status
  information collected in the Deploy Status table (KDYDYSTS).
  
  When the tacmd getdeploystatus command output shows more than
  10000+ deployments (failed, pending, successful, ? etc) , the
  capacity of the deploy processing to manage the update of this
  table in a FTO environment where both Mirror and HUB can
  exchange roles rapidly could lead to memory exhausting if
  queries of the tables are done on a massive scale one at a time.
  
  
  RECREATE INSTRUCTIONS:
  
  Install ITM 622 on TEMS and Mirror
  Install 12 RTEMS with Backups
  Install OS Agent on 20,000 endpoints on VM system.
  Install Non-Agent on 20,000 endpoints to modify OS Agent .ver
  file to force repeated installations to same machine.
  Run above steps for 1 month.
  

Local fix

• Create cron job to execute 'tacmd cleardeploystatus -s' command
  with perhaps daily frequency to cleanse deploy table.
  

Problem summary

• Add a feature to allow for automated clearing of completed
  transactions in the Deployment Status table.
  
  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

• New code was added to automate clearing of completed
  transactions in the Deployment Status table.
  
  Install Actions
  
  Each time you use tacmd or use the Tivoli Enterprise Portal to
  remotely manage a monitoring agent, information about the
  transaction is preserved in the monitoring server's Deployment
  Status table. To make it easier to manage the contents of this
  table, especially in large enterprises, you can schedule the
  periodic removal of completed transactions from the table.
  Enabling this feature allows you to review completed deployment
  transactions at opportune times as well as reduce the amount of
  monitoring server overhead by maintaining a modest table size.
  
  To schedule periodic cleansing of completed transactions from
  the Deployment Status table, you specify how often you want the
  cleansing to occur. Add the environment variable
  "CLEARDEPLOYSTATUSFREQ" to the monitoring server's configuration
  file to enable automated cleansing at startup. Set its value to
  the number of hours you want between each cleansing run. You can
  also use the IBM Tivoli Monitoring Service Console to set the
  clearing interval or disable the cleaning altogether at anytime.
  When automated clearing is enabled, the monitoring server
  automatically finds deployment transactions that have completed,
  removes them from the Deployment Status table to reduce its
  size, and records information about the deleted transaction in a
  log file.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.3-TIV-ITM-FP0002
  

Temporary fix

• Manually invoke "tacmd cleardeploystatus -s" and "tacmd
  cleardeploystatus -f".
  

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

• R623 PSY

     UP