LO76164: ACL ERROR ON NAMES.NSF REPLICATION

APAR status

• Closed as fixed if next.

Error description

• To reproduce the problem. I am sure now that the adminsitration
  process has changed the acl of names.nsf.  To reproduce the
  problem and to finde the reason  I have done these steps:
  
  - I have added the user User1 into the acl of names.nsf on the
  Server01 (Server01 is the Administration server of names.nsf)
  - I have replicated the names.nsf with the Server02
  - The user User1 has been renamed from User1 to User2
  - The ACL of names.nsf has been changed correctly by Server01
  
  
  
  - I have changed the executing time of delayed Request on the
  Server02 from "Sun 00:00" to "Fri 22:00"
  
  
  - On Friday the Server02 has changed the acl of names.nsf by
  Server02
  
  
  
  I think that this adminp request has changed the Acl of
  names.nsf. It is  only request that has modified the names.nsf
  
  - in the log.nsf I could find only 2 entries related to User1
  
  
  05.07.2013 22:05:33   User1 does not appear in the Readers or
  Authors fields of any databases designating Server02 as their
  Administration Server
  
  05.07.2013 22:03:25   Admin Process: User1 does not appear in
  design elements of any databases designating Server02 as their
  Administration Server
  
  My question: Why does this request change the ACL of names.nsf?
  

Local fix

• Nothing
  

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# SHJR99GJLN.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

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

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

Fix information

Applicable component levels

• R853 PSN

     UP