RNL (Active)

Restriction: Only relevant in an Enterprise Server Cluster environment.

A resource name list (RNL) is equivalent to global resource sharing (GRS). In an Enterprise Server CLUSTER these RNLs are used to determine how to treat the resources referenced by these RNLs. All RNLs are defined in the RNL descriptor file (ESCLRNLs.cfg) . At the start up of the Global Lock Manager (GLM) region, RNLs are verified and loaded in the GLM and pushed to all cluster participants during the initial cluster handshake. Once these initial definitions are installed, the RNLs can be updated on the GLM only by using the ACTIVE page. The GLM will push the changes to all cluster participants.

See RNL Support for more information on RNLs.

Use this page to view the RNLs available in this Enterprise Server Cluster member.

Details: Click this to display detailed information for the RNLs.

The information in this row displays the entire RNL definition:

Sequence

Indicates the position of this RNL in the global RNLs list.

RNL

Set to Include or Exclude.

Include - The SYSTEM inclusion RNL lists SYSTEM scope resources that you want the system to treat as global resources.
Exclude - The SYSTEMS exclusion RNL lists SYSTEMS scope resources that you want GRS to treat as local resources.

If an INCLUDE RNL matches the RNAME, the EXCLUDE list is searched, for example:

RNLDEF RNL(INCL) TYPE(Pattern) QNAME(SYSDSN) RNAME(SYS1.*)
RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.PRD2)

Any file starting with SYS1.* would be treated as a global resource except for a file starting with SYS.PRD2.

Type

Specifies the type of resource name entry being defined in the RNL:

Specific - you must specify a QNAME (major name) and an RNAME (minor name) for the resource.
Generic - indicates that the resource name in the RNL is a generic criteria, for example:
```
RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.PRD2)
```
Means that all files starting with SYS1.PROD2 will be a GLOBAL resources.
Pattern - indicates that the resource name in the RNL entry is a pattern that must fit the resource name specified on the ENQ request.
You can use wildcard characters (* or ?) in either part of the resource name:

*

Allows matching for a substring of any characters and for any length, including zero.

?

Allows matching for any single character.

QNAME

Set to SYSDSN.

RName

Resource name target of the include or exclude lock.