How You Convert RNL Specifications to CA MII Statements › Map RNL Specifications to CA MII QNAME Statements

Map RNL Specifications to CA MII QNAME Statements

In GRS, resource selection is accomplished with the use of three RNLs:

• SYSTEM inclusion RNL. This list is used to promote ENQs issued with a scope of SYSTEM to a scope of SYSTEMS; that is, force propagation.
• SYSTEMS exclusion RNL. This list is used to demote ENQs (or RESERVEs) issued with a scope of SYSTEMS to a scope of SYSTEM, that is, do not propagate.
• RESERVE conversion RNL. This list is used to suppress hardware RESERVE requests and allow the scope of SYSTEMS to remain.

In GRS RNL entries, the resources can be specific or generic.

• Specific means that the QNAME and RNAME of the request must exactly match the RNL specification or the RNL will not take effect.
• Generic means that the RNL takes effect if the QNAME and RNAME of the request match the RNL specification up to the length specified. In other words, generic entries are resource prefixes.

In CA MII, all resource selection is accomplished using statements specified in the MIMQNAME list. Exceptions, if required, are specified in the GDIEXMPT list.

Examples:

1. The following GRS RNL specifies that all ENQ requests issued with QNAME SYSDSN and scope SYSTEM will be promoted to SYSTEMS, and therefore will be propagated:

   RNLDEF RNL (INC) TYPE (GENERIC) QNAME (SYSDSN)
   

   The following CA MII QNAME statement produces similar results:

   QNAME SYSDSN SCOPE=SYSTEM GDIF=YES

2. The following GRS RNL specifies that ENQ requests issued with QNAME SYSDSN and RNAME 'SYS1.LOGREC' and whose scopes are (or are INCLuded, or promoted to) SYSTEMS will be downgraded to SYSTEM and will not be propagated:

   RNLDEF RNL (EXCL) TYPE (SPECIFIC) QNAME (SYSDSN) RNAME (SYS1.LOGREC)
   

   The following CA MII EXEMPT statement produces similar results:

   LOCAL QNAME=SYSDSN RNAME=SYS1.LOGREC