IC84985: HSM FOR WINDOWS RECONCILE DOESN'T CONTINUE AFTER CLUSTER FAILOVER

APAR status

• Closed as program error.

Error description

• HSM Monitor Service Reconcile doesn't continue after cluster
  failover.
  
  Problem Description:
  When HSM Monitor Service runs reconciliation on a cluster node
  and failover occurs, reconciliation will not continue on new
  node.
  
  Affected Products:
  Tivoli Storage Manager HSM for Windows versions 6.3.0.0 and
  6.3.0.1.
  
  Customer/L2 diagnostics:
  H:\>dsmhsmclc q
  Command Line HSM Reconcile and Threshold Migration Interface -
  Version 6, Release 3, Level 0.1
  (c) Copyright by IBM Corporation and other(s) 2005, 2012. All
  Rights Reserved
  
  Common Configuration:
  Number of Max Reconcile Processes:      3
  Number of Max Threshold Processes:      3
  Path to volume:                         H:\
  Configuration for Reconcile:
          Time for next Reconcile:                07/26/2012 10:19
          Reconcile Interval(hours):              720
          Reconcile now:                          NO
          Reconcile running:                      YES
          File Space List:                        All File Spaces
          Remote Server List:
  Configuration for Threshold Migration:
          Not configured
  Highest return code was 0
  
  Reconcile running is displayed YES, but reconcile will not
  actually start on the volume 'H'.
  
  Additional Keywords: none
  
  Initial Impact: Reconcile process is not started after failover.
  

Local fix

• Unconfigure volume, configure it again and set reconcile now.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: TSM HSM for Windows Client Versions          *
  *                 6.3.0.0 and 6.3.0.1                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * For detailed description see ERROR DESCRIPTION               *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.           *
  ****************************************************************
  

Problem conclusion

• The problem has been solved.
  

Temporary fix

• See LOCAL 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

  TSM HSM FOR WIN

• Fixed component ID

  5698ICNCL

Applicable component levels

• R630 PSY

     UP