z/OS allows symbolics to be used in some circumstances. Does ACF2 allow symbolics to be used in the ACFFDR? In this way one ACFFDR can be used with different database names used via the symbolic.
Symbolics are allowed in the ACFFDR. Code up the database names with the symbolic &&SYSNAME or any other relevant system symbolic. For example, the ACF2 usermod UM99901 might look like:
++SRCUPD (ACFFDR) DISTLIB(AAX1SRC) . ./ CHANGE NAME=ACFFDR @CSVC ALTER=222,VALD=221 @DDSN PRIMARY, ** DEFAULT GROUP NDX RULE='SYS1.&&SYSNAME..RULES', ** RULES CLUSTER LID='SYS1.&&SYSNAME..LOGONIDS', ** LOGONID CLUSTER INFO='SYS1.&&SYSNAME..INFOSTG', ** GEN RESOURCE CLSTR BRULE='SYS1.&&SYSNAME..BKRULES', ** RULES BACKUP BLID='SYS1.&&SYSNAME..BKLIDS', ** LOGONIDS BACKUP BINFO='SYS1.&&SYSNAME..BKINFO' ** RESOURCE BACKUP
Then at allocation time, either during the IPL, or a restart of ACF2, the &SYSNAME will be resolved by z/OS. After the change, the SHOW command on that system will show the actual name in use, and the symbolic in the ACFFDR part of the command output.
SHOW DDSN -- ACF2 DYNAMIC DATASET NAMES SPECIFIED -- DDSNS PRIMARY DEFAULTED AT STARTUP. DSNS IN USE ARE: RULES= SYS1.xxxx.RULES LOGONIDS= SYS1.xxxx.LOGONIDS INFOSTG= SYS1.xxxx.INFOSTG BACKRULE= SYS1.xxxx.BKRULES BACKLID= SYS1.xxxx.BKLIDS BACKINFO= SYS1.xxxx.BKINFO DDSN LISTS DEFINED IN FDR ARE: PRIMARY RULES= SYS1.&SYSNAME..RULES LOGONIDS= SYS1.&SYSNAME..LOGONIDS INFOSTG= SYS1.&SYSNAME..INFOSTG BACKRULE= SYS1.&SYSNAME..BKRULES BACKLID= SYS1.&SYSNAME..BKLIDS BACKINFO= SYS1.&SYSNAME..BKINFO
Normal standards apply to the datasets in regards to the ACF2 databases. The databases should be on a separate dasd volume then what volume that ACF2 is cataloged in. We also recommend that the databases be in their own catalog.