ACF2 databases shared between 2 LPARs without implementing MIM or GRS
search cancel

ACF2 databases shared between 2 LPARs without implementing MIM or GRS

book

Article ID: 247849

calendar_today

Updated On:

Products

ACF2 ACF2 - MISC ACF2 - z/OS

Issue/Introduction

Can ACF2 databases be shared between two LPARs without implementing MIM DASD or GRS ?

Environment

Component : ACF2 for z/OS

Resolution

GRS is automatically included with z/OS and ACF2 documentation provides details of the exclude list of entries that are required in GRS.

Details can be found at at Prepare for Shared DASD

The doc includes the following minimum GRS setup:

A sample exclude list for GRS is constructed as follows:

* LABEL TYPE, MINOR‑LENGTH, MAJOR‑NAME, MINOR‑NAME
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF2.LOGONIDS)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF2.ALTLIDS)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF2.RULES)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF2.ALTRULES)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF2.INFOSTG)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(ACF2.ALTINFO)
RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(ACFVSAM)
RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSVSAM) RNAME(ACF2)
RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(ACF2)

The last GRS exclude entry can be used if the RNAME is only used with the database clusters.