The RNLs on all systems in the complex must be the same; that is, each RNL on each system must contain the same resource name entries, and these resource name entries must appear in the same order.

The GRSRNLxx parmlib member is used to define the RNLs. During IPL, specifying the desired member(s) on the GRSRNL system parameter tells global resource serialization where it can find the RNLs. When the complex matches the sysplex, issuing the SET GRSRNL command tells global resource serialization where it can find the updated RNLs. However, the SET GRSRNL command does not work on any system in a mixed complex. Once you remove non-sysplex systems from the complex, so the sysplex matches the complex, you can use the SET GRSRNL command. See Dynamic RNL processing for further information about using the SET GRSRNL command.

IBM® supplies a default, member GRSRNL00 of SYS1.PARMLIB, that defines the default RNLs. See Figure 1.

You can either use GRSRNL00 as is, modify it, or create additional GRSRNLxx members. You might find it useful to leave GRSRNL00 as is and use one or more separate members to define your own entries. Separating the IBM-supplied entries from your installation-dependent entries can make future migration easier. You might also find it useful to set up one member for generic entries and another member for specific entries.

z/OS MVS Initialization and Tuning Reference contains detailed information about specifying the entries in GRSRNLxx. The worksheet shown in Table 1 lists the RNL entries IBM supplies in GRSRNL00 and includes blank slots for your own entries.

Test GRSRNLxx carefully to ensure that it does not include syntax errors. In SYS1.SAMPLIB, IBM supplies a syntax checker that can detect such errors. Member SPPINST of SYS1.SAMPLIB contains information about using the syntax checker. To minimize the testing, create a single GRSRNLxx member, test it, and then copy it to the parmlib of all systems.