A Resource Name List (RNL) is used to specify the scope of a lock which can be local or global and can be used in a PAC. All
RNLs are defined in the RNL descriptor file (ESCLRNLs.cfg). At the start up of the PAC, RNLs are verified and loaded into the member regions. Once these initial definitions are installed,
the RNLs can be updated in the PAC only by using the Active RNL page. The PAC will push the changes to all member regions.
Use this page to view the RNLs available in this PAC member:
- Indicates the position of this RNL in the global RNLs list.
- Set to Include or Exclude:
- The SYSTEM inclusion RNL lists SYSTEM scope resources that you want the system to treat as global resources.
- 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
- Specifies the type of resource name entry being defined in the RNL:
- You must specify a QNAME (major name) and an RNAME (minor name) for the resource.
- Indicates that the resource name in the RNL is a generic criteria, for example:
RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN) RNAME(SYS1.PRD2)
This means that all files starting with
SYS1.PROD2 will be a GLOBAL resources.
- 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: - -
- Enables matching for a substring of any characters and for any length, including zero.
- Enables matching for any single character.
- This is the major name for the resource.
- This is the minor name for the resource.