IZ87528: TACMD LISTACTION/BULKEXPORTSIT COMMANDS DO NOT WORK PROPERLY WITH YN AGENTS

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

• Environment:
  
  Affected OS:  Any that provide CLI/tacmd interface.
  Releases of ITM:  All
  
  Problem Description:
  
  When using tacmd commands such as bulkexportsit and listaction
  entries in the TEMS database which have an ORed affinity string
  (not the base node/subnode affinity) will not be returned.  So
  currently
  
  tacmd listactions -t yn
  
  will only return data which has the base affinities.  All
  listactions with an ORed affinity (meaning that action applies
  to multiple subnodes) will not be listed.
  
  
  The current function used by CLI only returns the base
  affinities.  A new function needs to be provided by TEMS which
  will return a superset.  Once this function is available, CLI
  will need to take advantage of it.  This will allow for not only
  base node/subnode data to be returned but also data which has
  ORed affinities.
  
  Detailed Recreation Procedure:
  
  To recreate install the YN application support (I used
  CZAWE1EN for windows)
  
  Run tacmd listactions
  
  Only a subset is provided because most actions are using the
  ORed affinity.
  

Local fix

• Only option is to use either kdstsns or SOAP and select
  on the ORed affinities.
  

Problem summary

• tacmd listactions/bulkexportsit commands do not work properly
  with YN agents.
  
  When using tacmd commands such as bulkexportsit and listaction
  entries in the management server database which have an ORed
  affinity string (not the base node/subnode affinity) will not be
  returned.  So currently
  tacmd listactions -t yn
  
  will only return data which has the base affinities.  All
  listactions with an ORed affinity (meaning that action applies
  to multiple subnodes) will not be listed.
  

Problem conclusion

• The solution is to leverage a new API provided by the management
  server with APAR IZ88832 to properly retrieve combined
  affinities.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-TIV-ITM-FP0006
  

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