ACFCC202 ACF2 CACHE SYNCHRONIZATION DATASET LOCKED BY ANOTHER COMPLEX.

Products

• ACF2 - z/OS

Issue/Introduction

What is causing this error message sporadically?

ACFCC202 ACF2 CACHE SYNCHRONIZATION DATASET LOCKED BY ANOTHER COMPLEX.

 

Environment

Release : 16.0

Resolution

An occasional ACFCC202 may be ok based on the activity level and workload on the LPAR. If the message occurs repeatedly, then SYNCRESET command should be issued. The SYNCRESET should NOT be issued for the occasional ACFCC202.                            
                                                                             
The cause of this message could be related to many updates to the sync file when the LPAR started shutting down. If the sync file was still locked by some other LPAR then an ACFCC202 would be issued for every potential update to the file, and at the end of every polling interval there would be another attempt to make the updates, resulting in another round of ACFCC202s.                        
                                                                             
List the GSO SYNCOPTS used by each LPAR in the SYSPLEX. If they have unique sysids, then ensure that each SYNCOPTS specifies a reasonable POLLINTV. If you are using the default of 5 seconds, consider increasing it to 10 seconds in each SYNCOPTS record as shown below:

- SET C(GSO) SYSID(xxxx)          => Replace SYSID according to the LPAR name 

- CHANGE SYNCOPTS POLLINTV(10) 

- F ACF2,REFRESH(SYNCOPTS)