How can ACF2 VM Databases be shared between multiple z/VM systems?
The Database Synchronization Component (DSC) is specifically designed for sites that are sharing ACF2 for VM databases between VM and z/OS or between multiple z/VM systems. The DSC allows synchronization of ACF2 for VM database changes between VM and z/OS systems using CAICCI (with VTAM or TCP/IP) as the communications method. On the z/OS system the Command Propagation Facility (CPF) is required for the Database Synchronization Component (DSC). CPF on the z/OS system lets you send changes made to ACF2 databases on a z/OS system to the corresponding databases on a VM system, and conversely.
All updates, inserts, changes, and deletes you make to any ACF2 for VM record, from z/OS or VM, are shipped (propagated) to the target systems. You can journal any change you make with DSC to a log file. In case one of the two systems is unavailable, the Database Synchronization Component service machine stores the request in a communication log file until the change is shipped to the target system for processing. When the system becomes available and the necessary connections are in place, the Database Synchronization Component service machine ships any changes that were logged and not processed.
Details for the z/VM Database Synchronization Component (DSC) can be found in the r12 ACF2 for z/VM Installation Guide in Chapter 7: Installation Options, section "Database Synchronization Component' page 180. The z/VM Database Synchronization Component (DSC) requires z/VM CA-CIS Services.
Details regarding the z/OS Command Propagation Facility (CPF) can be found in ACF2 for z/OS - 16.0 documentation in section CPF Consideration
The following are considerations when running ACF2 VM DSC over TCP/IP:
Documentation for ACF2 r12 for z/VM
Details on the CCI support for TCP/IP can be found in the CA-CIS Getting Started Guide