If you are sharing a RACF® database across systems through DASD, you should consider converting the reserves used to serialize the volume, as long as all systems that access the RACF database are MVS™ systems that are part of the same Global Resource Serialization complex. For example, if a VM system is sharing access to the RACF database, you cannot convert the reserves.

To convert the reserves, place a generic entry for SYSZRACF in the reserve conversion RNL. In a mixed complex (meaning at least one system in the global resource serialization complex is outside of the multisystem sysplex), when you convert the SYSZRACF reserves you must reply to any global resource serialization messages related to ring disruptions or restarts from an MCS console. Failure to reply or replying to the message after issuing an operator command might result in a system hang condition.

In any case, do not put an entry that begins with 'SYSZRACF' or 'SYSZRAC2' in the SYSTEM inclusion RNL.

Guideline: IBM® recommends moving all catalog and VSAM data sets off any volume that holds a RACF database.