ACF2 DATABASE SHARING with two LPARs, each with their own databases.

Products

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

Issue/Introduction

A site has two LPARS which are NOT currently in a SYSPLEX together. CA MIM is used for resource serialization, and each lpar has its 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?

Environment

Release:
Component: ACF2MS

Resolution

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 then the rules on both will work, but consideration must be given to whether or not the rules from each lpar need to be merged into a single ACF2 RULES and INFOSTG database. If the UID strings are different then the databases cannot be merged and the same rules cannot be used 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 the LOGONID databases must be merged.

Merging ACF2 databases 
The ACF2 databases are standard VSAM files and can be merged, but it must be decided how duplicate records are handled. IDCAMS REPRO is the recommended method of merging acf2 databases. It provides a choice of one of the following:                       
                                                                             
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 some duplicate records are to be used from one database, and other duplicate records are to be used from the other database, the sequential database copies must be edited prior to the merge. 

As far as MIM the syntax for the MIM EXCLUDE statement are as follows:     
                                                             
 LOCAL    QNAME=SYSDSN,RNAME=hlq.primary.INFOSTG            
 LOCAL    QNAME=SYSDSN,RNAME=hlq.primary.LOGONIDS           
 LOCAL    QNAME=SYSDSN,RNAME=hlq.primary.RULES              
 LOCAL    QNAME=SYSDSN,RNAME=hlq.alternat.INFOSTG           
 LOCAL    QNAME=SYSDSN,RNAME=hlq.alternat.LOGONIDS          
 LOCAL    QNAME=SYSDSN,RNAME=hlq.alternat.RULES             
 LOCAL    QNAME=SYSVSAM,RNAME=hlq.primary.*                 
 LOCAL    QNAME=SYSVSAM,RNAME=hlq.alternat.*  
 LOCAL    QNAME=ACFVSAM                                                    
                                                                           
where "hlq.primary" and "hlq.alternat" are the qualifer levels for the appropriate 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"  in the ACF2 documentation provides additional considerations for shared ACF2 Databases.