How do I implement ACF2 Shared Databases on two lpars that have their own set of ACF2 Databases?

Document ID : KB000122712
Last Modified Date : 06/12/2018
Show Technical Document Details
Question:
A site with two LPARs, which are NOT currently in a SYSPLEX together, using CA MIM for resource serialization, each LPAR with it's own ACF2 Databases. The site will be implementing a single set of ACF2 databases to be shared between the two  lpars. What are the considerations and/or requirements for sharing the ACF2 Databases between two LPARs? Do they have to be in a SYSPLEX together? Are there MIM considerations? Is there a "how to" document available for accomplishing this?
Answer:
There are several issues to consider when implementing shared databases between two lpars that currently have their own ACF2 databases. 
  1. If both systems have the same UID string that the rules on both system will work but you will need to consider if the rules from each lpar need to be merged into a single ACF2 RULES and INFOSTG database. If the UID strings are different then cannot merge the databases or use the same rules for both lpars unless the ACFFDR is modified to insure both lpars have the same UID string.
  2. If both systems use a different SYSID then the ACF2 GSO records that are stored must be merged into a single ACF2 INFOSTG database.
  3. If the LOGONID databases are different then you would need to merge the LOGONID databases.
Merging ACF2 
The ACF2 databases are standard VSAM files and can be merged however a decision would need to be made to determine how duplicate records are handled.IDCAMS REPRO is the recommended method of merging acf2 databases but you must decide how to process duplicate records.                     
                                                                             
With NOREPLACE, records from INFILE (or INDATASET) will not overwrite a duplicate record in the target dataset specified in OUTFILE (or OUTDATASET). 
                                                                             
With REPLACE, records from INFILE (or INDATASET) will overwrite a duplicate record in the target dataset specified in OUTFILE (or OUTDATASET).           

In a situation where you want some duplicate records to be used from one database and other duplicate  records to be used from the other database you would need to edit the sequential database copies prior to the merge. 

As far as MIM the syntax for the MIM EXCLUDE statement are as follows:     
                                                             
 LOCAL    QNAME=SYSDSN,RNAME=your.primary.INFOSTG            
 LOCAL    QNAME=SYSDSN,RNAME=your.primary.LOGONIDS           
 LOCAL    QNAME=SYSDSN,RNAME=your.primary.RULES              
 LOCAL    QNAME=SYSDSN,RNAME=your.alternat.INFOSTG           
 LOCAL    QNAME=SYSDSN,RNAME=your.alternat.LOGONIDS          
 LOCAL    QNAME=SYSDSN,RNAME=your.alternat.RULES             
 LOCAL    QNAME=SYSVSAM,RNAME=your.primary.*                 
 LOCAL    QNAME=SYSVSAM,RNAME=your.alternat.*  
 LOCAL    QNAME=ACFVSAM                                                    
                                                                           
where "your.primary" and "your.alternat" are the qualifer levels for your ACF2 primary and alternate database DSNs.                                  
                                                                           
Also please note the following information regarding the MIM logonid. The MIM logonid should have NO-SMC set, the default is NONO-SMC. To change this setting in the logonid, the TSO, ACF command processor can be used as follows.                                                        
                                                                           
  ACF                                                                      
  SET LID                                                                  
  CHANGE logonid NO-SMC                                                                  

Lastly section "Prepare for Shared DASD (Optional)" in the ACF2 documentation provides additional considerations for shared ACF2 Databases.