Keeping ACF2 databases synced between multiple LPARs
Article ID: 258313
ACF2 - z/OSACF2ACF2 - MISC
What are the options for keeping ACF2 databases synced between multiple LPARs?
Release : 16.0
The options available for keeping the ACF2 databases in sync are:
Creating a single shared database.
This is the only true method of keeping all records the same on both systems. See Create ACF2 VSAM Databases section of ACF2 documentation for shared database considerations.
Periodically use the backups from one system to copy into another system.
This would keep the databases in sync at the point of the copy, but there would be a span of time between copy processes where the databases could potentially fall out of sync.
The databases being copied to cannot be active during the time of the copy.
Using CPF to sync rule updates and password changes.
The databases could still be out of sync, but relevant changes can be sent to multiple LPARs. For example, a one way communication from PROD to DEV systems is set up. Changes could still be made on DEV that don't get pushed to PROD. This allows changes to be made to DEV without impacting PROD, but the databases would still contain different information. In this example, users would need to be instructed to only change passwords on PROD if password sync was one of the goals for using CPF.
Only certain commands will be processed. The following commands will not be processed:
CHKCERT COMPILE DECOMPILE EXPORT GENCERT GENREQ ROLLOVER SET SHOW STORE
If a site uses the COMPILE, DECOMPILE and STORE method for rule updates, those commands wouldn't be processed. This may mean changing site process to only use the RECKEY command when making rule updates.