RNL Support

• RNL=NO
• GRSRNL=EXCLUDE
• GRS=NONE
• The ISGNQXIT or ISGNQXITFAST exit

CASSI9025I All RNLDEFs received and installed from ES Cluster Manager GML_NAME

An RNL identifier

• RNL(EXCL) for the SYSTEM exclusion list
• RNL(INCL) for the SYSTEM inclusion list

An entry type indicator

• TYPE(SPECIFIC) - the entry is a specific name
• TYPE(GENERIC) - the entry is a generic name
• TYPE(PATTERN) - the entry is a pattern name

A qname

• QNAME(QUEUE_NAME)

  Enterprise Server Clusters only process three queue names: SYSZJOBD, SYSZJOBN and SYSZDSN. RNLs are only used to define the scope of the SYSZDNS resources. SYSZJOBD and SYSZJOBN are always global (scope = servers).

An rname

• RNAME(Resource_name)

  As the only QNAME used for RNLs is a SYSZDSN, the resource name maximum length is 44.

• No restrictions on columns, but an RNLDEF must be contained in a single line.
• No support for comments.
• Each RNLDEF statement is defined as beginning with the characters RNLDEF and ends at the end of the line.
• Each RNLDEF statement must contain, in any order, the RNL, TYPE, QNAME and RNAME parameters. The only exception to this is:
  • The RNAME parameter may be omitted it TYPE(GENERIC) is specified for a generic QNAME resource. For example:

    RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSZDSN) 

    This will result in the scope set to local for all SYSZDSN.
• You can put a blank anywhere except within a keyword or a specified value.
• There is no verification on the RNAME.
• Formats such as RNAME(X'19') are not supported.
• A specific resource name entry matches a search argument only when they are exactly the same. A match occurs only when the length of the RNAME value on the RNLDEF statement is the same as the length of the RNAME value coded.