IBM Support

SE69471 - OSP-OTHER-INCORROUT CLUSTER ADMINISTRATIVE DOMAIN SHOWS
CONSISTENT ON MRE WHEN IT REALLY SHOULD BE INCONSISTENT.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 APAR (Authorized Program Analysis Report)

Abstract

OSP-OTHER-INCORROUT CLUSTER ADMINISTRATIVE DOMAIN SHOWS
CONSISTENT ON MRE WHEN IT REALLY SHOULD BE INCONSISTENT.

Error Description

In a cluster administrative domain environment, an MRE          
(Monitored Resource Entry) could be seen as Consistent when in  
reality the MRE could be Inconsistent.                          
                                                               
It has been discovered that there could be an inconsistency on  
an admin domain MRE while a local status is showing Update      
Pending, yet the global status shows Consistent.                
If there is an Update Pending, then technically the global      
status should be Inconsistent until there is no longer anything
in Update Pending.                                              
It has also been seen that if there is a lock on a MRE at the  
time of a change, the QPRFSYNCH job will not be able to obtain  
the lock and make the appropriate change. During this time,    
local status would be Update Pending while global status shows  
Consistent. The local change has been made but may not have    
propagated to all target nodes in the admin domain. The only    
way to get out of this state is to either attempt another      
update to the MRE or end and restart the admin domain.          
                                                               
Code will be enhanced to provide more accurate feedback about  
the global status of the MRE as appropriate.                    

Problem Summary

In a cluster administrative domain environment, a Monitored    
Resource Entry (MRE) could display a global status of Consistent
when the global status should be Inconsistent.                  
When the cluster administrative domain is not able to access a  
monitored resource after receiving a change notification for    
that resource the local status of the resource is changed to    
Update Pending, but the global status is not changed.  The      
update of the resource is not sent to other nodes in the cluster
administrative domain, so the resource will not have the same  
attribute values on each node in the cluster administrative    
domain.                                                        
The most common reason that the cluster administrative domain  
would not be able to access a monitored resource is that a      
process has an exclusive lock on the resource.                  

Problem Conclusion

The global status of an MRE will be shown as Inconsistent when  
one or more nodes have a local status of Update Pending.        

Temporary Fix

Comments

Circumvention


For each resource which should have a global status of          

Inconsistent: first ensure that no processes have an exclusive  
lock on the resource, then either update the resource or end the
cluster administrative domain and start it again.  Restarting  
the cluster administrative domain will resolve the problem for  
all affected resources, assuming that no process retains an    
exclusive lock on the resource.                                

PTFs Available

R720 SI68000 PTF Cover Letter   8249
R730 SI68033 PTF Cover Letter   9116

Affected Modules

         
         

Affected Publications

Summary Information

Status............................................ CLOSED PER
HIPER........................................... No
Component.................................. 5770SS100
Failing Module.......................... RCHMGR
Reported Release................... R720
Duplicate Of..............................




System i Support

IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.3.0"},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15Q","label":"APARs - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R2M0;V7R3M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
10 May 2019