Sharing a database with sysplex communication in non

Before you enable your RACF® system for sysplex communication in non–data sharing mode, the system must meet the following requirements:

The system must be a single-system sysplex or a member of a multisystem sysplex (that is, not in XCF-local mode).
If you are using the MVS™ global resource serialization function to serialize system resources, the major names SYSZRACF and SYSZRAC2 cannot be in the exclusion resource name list (RNL).
- If you have SYSZRAC2 in your RNL, you must schedule a sysplex-wide IPL to remove it before running RACF in sysplex communication or datasharing mode, or your RACF database might become corrupted. You cannot remove this name dynamically, because RACF maintains a permanent ENQ on this resource.
- If you have SYSZRACF in your RNL, you can remove it dynamically if you first stop the RACF subsystem on all systems in the global resource serialization complex. SYSZRACF (minor name of RACF) is held continuously if a RACF subsystem is running, and stopping the RACF subsystems releases the ENQ.
If you are using a non-IBM global resource serialization product to serialize system resources, be aware that resources with major names SYSZRACF and SYSZRAC2 might be requested with SCOPE=SYSTEMS. You must ensure that SCOPE=SYSTEMS is honored for the requests.
As noted in Shared database considerations, in non–data sharing mode hardware RESERVEs are used to serialize database access. If using the MVS global resource serialization function, you could consider converting the RESERVEs to ENQs by placing a generic entry for SYSZRACF in the RESERVE conversion resource name list (RNL). For more information, see Using the global resource serialization function.
The system and all systems it shares a database with meet the requirements for sharing a database:
- The database resides on shared DASD.
- The data set name table (ICHRDSNT) is compatible on all sharing systems.
- The database range table (ICHRRNG) is identical on all sharing systems.
- The class descriptor table (ICHRRCDE) is compatible on all sharing systems.

Guideline: All systems enabled for sysplex communication and sharing the same RACF database should be members of the same sysplex. Doing this prepares you for RACF sysplex data sharing, and ensures that commands are propagated to all members of the sysplex.