Preparing for Installation › Pre-Installation Considerations › GRS Considerations

GRS Considerations

If your site uses GRS, include a CONVERSION RNL for each master file, as follows:

RNLDEF RNL(CON) TYPE(GENERIC) QNAME(ADRPRDCT)
RNAME(master.file.dsn)

A GENERIC type RNAME of the data set name is defined to cover all of the resource names listed in the following table.

Alternatively, you can define multiple master files under one RNLDEF by specifying the high-level data set name qualifiers, as follows:

RNLDEF RNL(CON) TYPE(GENERIC) QNAME(ADRPRDCT)
RNAME(master.file.qualifier)

A CONVERSION RNL is optional but recommended for BDAM or single-volume VSAM master files. A CONVERSION RNL is required for multi-volume VSAM master files.

For update processing (both batch and online), CA Librarian employs resource serialization to minimize the duration of enqueues and reserves issued on the master file.

The resources used are listed below in the order in which they are always claimed:

Important! In the VM/ESA and z/VM environment where LIB/CMS is installed, including ADRPRDCT in the GRS conversion RNL corrupts the master file. VM/ESA and z/VM users of CA Librarian share master files with z/OS and OS/390 users through the use of real and virtual RESERVE/RELEASE. If GRS intercepts and converts the CA Librarian-issued RESERVE commands, VM/ESA and z/VM users might not recognize simultaneous accesses from the z/OS and OS/390 system.