IV73470: RESOURCE GROUPS REMAIN IN STATUS "CONTROL=UNDEFINED" WITH OPERATIONALFLAGS=8152

4.1.1-TIV-SAMP-Linux64-FP0001
4.1.1-TIV-SAMP-AIX-FP0001
4.1.0-TIV-SAMP-AIX-FP0002
4.1.0-TIV-SAMP-Linux64-FP0002
4.1.0-TIV-SAMP-Linux-FP0002
3.2.2-TIV-SAMP-Linux-FP0009
3.2.2-TIV-SAMP-AIX-FP0009
3.2.2-TIV-SAMP-Solaris-FP0009
3.2.2-TIV-SAMP-Windows-FP0009
3.2.2-TIV-SAMP-Windows-FP0009
4.1.0-TIV-SAMP-AIX-FP0003
4.1.0-TIV-SAMP-Linux-FP0003
4.1.0-TIV-SAMP-Linux64-FP0003
4.1.0-TIV-SAMP-AIX-FP0006
4.1.0-TIV-SAMP-Linux-FP0006
4.1.0-TIV-SAMP-Linux64-FP0006
4.1.0-TIV-SAMP-AIX-FP0007
4.1.0-TIV-SAMP-Linux64-FP0007
SAMP4107_Verification_Signatures
4.1.1-TIV-SAMP-AIX-FP0000
4.1.1-TIV-SAMP-Linux64-FP0000
3.2.2-TIV-ITSAMP-FP0009, Tivoli System Automation for Multiplatforms
4.1.0-TIV-ITSAMP-FP0003, Tivoli System Automation for Multiplatforms
4.1.0-TIV-ITSAMP-FP0004, Tivoli System Automation for Multiplatforms

APAR status

• Closed as program error.

Error description

• When setting OperationalFlags=8152, resources may stuck in a
  status with "control=undefined".
  Normally this status is only a transition state, but here
  resource group state does not come out of status
  "control=undefined"
  
  
  If IBM.RecoveryRM gets result after subscription from
  IBM.AgileSystem or IBM.LogicalVolume resource and the Container
  attribute is NULL element (means 128 bit null), then there's no
  resource (means logical volume or volume group) depending on
  the just created resource.
  This is an implizite "DependsOn" relationship. Then the
  RecoveryRM creates an "empty" internal DependsOn relationship
  and moves to a worker queue the request to create relationship
  and the subscription for target resource (in case of logical
  volumes it's the corresponding volume group). During that time
  the dependencies cannot be read directly from the resource, the
  BINDER would take care of the file system and logical volumes,
  but not of the still unknown VG - if it would run.
  Therefore no BINDER run can be done for the time of "resource
  known" & "wait for target resource subscription results".
  

Local fix

• Stop domain forcefully with "stoprpdomain -f <Domain name>"
  After restart the problem is not seen again.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Tivoli System Automation for Multiplatforms
  * users using nested resource groups
  ****************************************************************
  * PROBLEM DESCRIPTION:
  * Resource groups remain in status 'Control=Undefined' when all
  * the following conditions are met in given order:
  *  1. OperationalFlags is set to 8152 (Secondary Subscription)
  *  2. domain/cluster is restarted
  *  3. policy with nested resource groups is activated
  *  4. RecoveryRM master is changing nodes
  * As a result the policy is not initialized and sub sequently no
  * automation actions will be performed.
  ****************************************************************
  * RECOMMENDATION:
  ****************************************************************
  

Problem conclusion

• The internal handling of the automation engine has been adjusted
  to address the problem. Now nested groups are correctly handled
  even with OperationalFlags set to 8152
  .
  The official fix for this problem is included in Tivoli System
  Automation for Multiplatforms 4.1 fix pack 2
  | 4.1.0-TIV-ITSAMP-FP0002 |
  .
  Additional Search Keywords
  .
  

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

  SA MULTIPLATFOR

• Fixed component ID

  5724M0000

Applicable component levels