ACF2 Cache Synchronizer Troubleshooting

Products

• ACF2
• ACF2 - MISC
• ACF2 - z/OS

Issue/Introduction

When sharing ACF2 databases between LPARs and caching is enabled, the synchronizer is responsible for making sure database changes issued on one LPAR are reflected in the LPAR where the ACF2 commands were not issued. When this fails to occur, below are steps to troubleshoot the error.  

Resolution

1. Verify that the CACHE and SYCHRONIZER are both active on all systems sharing the databases. This can be verified by an ACF2 'SHOW ACTIVE' command or by issuing an 'F ACF2,CACHE(STATUS)' command.
   
   
2. Verify that SHR-DASD is SUPPORTED on all systems. This can be verified by issuing an ACF2 'SHOW SYSTEMS' command.
   
   
3. Run an F ACF2,CACHE(STATUS) command and verify:
   
   
   1. There are no error messages pointing to a specific problem.
      
      
   2. All systems are using the same syncfile as shown in the ACFCC112 message.
      
      
4. If all of the above have been completed and everything looks as it should, then the next step is to delete and recreate the syncfile as it may have become corrupted.
   
   
   1. Stop the synchronizer on all systems that share databases: F ACF2,CACHESYN(STOP) 
      
      
   2. Delete and reallocate the syncfile. Considerations for creating the synchronization file can be found in Allocating the Synchronization File. 
      
      
   3. Re-start the synchronizer on all systems and re-test: F ACF2,CACHESYN(START)  
      
      
5. If the issue still persists after all steps have been followed, take a DUMP of the ACF2 address space on two systems where the issue is occurring and contact Broadcom Support.