IV07892: TACMD DOES NOT NOTIFY TEMS IS ACTING SECONDARY

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)

APAR status

• Closed as program error.

Error description

• Environment:
  
    ITM 622 FP4.
  
  Problem Description:
    When logging into tacmd there is no notification that the TEMS
  being
    connected to is now acting as the secondary.  Changes made via
  tacmd
    will be lost.
  
  Detailed Recreation Procedure:
    Install two TEMS and setup FTO.  Login to the backup, make
  changes.
  No notification, data is lost.
  
  Related Files and Output:
     N/A
  

Local fix

• Using kdstsns you can run this SQL:
  
  SELECT ANNOT
     FROM O4SRV.TGBLBRKR
  WHERE ENTRTYPE = 1;
  
  
  If on UNIX you can modify tacmd.  Add the export SQLLIB
  statement pointing to where the sql above is residing in a file
  and then run the kdstsns command.
  

Problem summary

• TACMD allows connection to secondary HUB.
  
  TACMD does not warn the user that they are connected to the
  secondary HUB.  When changes are made using TACMD connected to a
  mirror, those changes are lost.
  

Problem conclusion

• Modified TACMD so it will not allow a connection to a secondary
  HUB.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-TIV-ITM-FP0008
  

Temporary fix

• When using TACMD, always be certain to connect to the active
  primary HUB.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  OA39106

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R622 PSY

     UP