IJ33163: ACL MISMATCH BETWEEN PRIMARY AND SECONDARY SITE WHEN IAM MODE IS UPGRADED TO COMPLIANT OR COMPLIANT-PLUS

APAR status

• Closed as program error.

Error description

• This occurs on a compliant or compliant-plus
  mode fileset, when the immutable files
  inside them remain as is.
  When such files are taken for AFM replication,
  the files in the Resync/Recovery
  path can set immutable attribute at secondary
  and also remove the write flag.
  This ends up being seen as a data
  mismatch in terms of ACLs between the sites.
  

Local fix

Problem summary

• This occurs on a compliant or compliant-plus
  mode fileset, when the immutable files
  inside them remain as is.
  When such files are taken for AFM replication,
  the files in the Resync/Recovery
  path can set immutable attribute at secondary
  and also remove the write flag.
  This ends up being seen as a data
  mismatch in terms of ACLs between the sites.
  

Problem conclusion

• Benefits of the solution:
  Consistency of ACLs between
  the Primary and Secondary sites for
  immutable files, when IAM mode gets upgraded.
  
  Work around
  None
  
  Problem trigger:
  None
  
  Symptom:
  Unexpected Behavior
  
  Platforms affected:
  ALL Linux OS environments
  
  Functional Area affected:
  AFM
  
  Customer Impact:
  Suggested
  

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

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels