Note: This example is intended solely for the purpose of illustrating how you can convert RNL specifications to CA MII QNAME statements. It is not intended to be a recommendation for implementing DFSMS serialization in CA MII. As with any product, contact the vendor of that product to obtain the most current QNAME or RNL recommendations.
In the z/OS V1R12.0 DFSMShsm Implementation and Customization guide, IBM gives an example of the RNL definitions required when running DFSMShsm with CDSR=YES and DFHSMDATASETSERIALIZATION options, and when the RESERVE for the JOURNAL file is not converted. The RNL definitions for this configuration are as follows:
RNLDEF RNL (EXCL) TYPE (GENERIC) QNAME (ARCAUDIT) RNLDEF RNL (EXCL) TYPE (GENERIC) QNAME (ARCBACK) RNLDEF RNL (EXCL) TYPE (GENERIC) QNAME (ARCGPA) RNLDEF RNL (EXCL) TYPE (GENERIC) QNAME (ARCGPAL) RNLDEF RNL (EXCL) TYPE (GENERIC) QNAME (ARCUPDT) RNLDEF RNL (CON) TYPE (GENERIC) QNAME (ARCBACV) RNLDEF RNL (CON) TYPE (GENERIC) QNAME (ARCMIGV) RNLDEF RNL (INC) TYPE (GENERIC) QNAME (SYSDSN) RNLDEF RNL (EXCL) TYPE (GENERIC) QNAME (SYSVTOC)
In CA MII, code the following statements in your MIMQNAME list:
ARCAUDIT GDIF=NO SCOPE=RESERVES EXEMPT=NO RESERVES=KEEP ARCBACK GDIF=NO SCOPE=RESERVES EXEMPT=NO RESERVES=KEEP ARCGPA GDIF=NO SCOPE=RESERVES EXEMPT=NO RESERVES=KEEP ARCGPAL GDIF=NO SCOPE=RESERVES EXEMPT=NO RESERVES=KEEP ARCUPDT GDIF=NO SCOPE=RESERVES EXEMPT=NO RESERVES=KEEP ARCBACV GDIF=YES SCOPE=RESERVES EXEMPT=NO RESERVES=CONVERT ARCMIGV GDIF=YES SCOPE=RESERVES EXEMPT=NO RESERVES=CONVERT ARCENQG GDIF=YES SCOPE=SYSTEMS EXEMPT=NO SYSDSN GDIF=YES SCOPE=SYSTEM EXEMPT=NO SYSVTOC GDIF=NO SCOPE=RESERVES EXEMPT=NO RESERVES=KEEP
Note that there is no RNL entry for the ARCENQG QNAME, but there is an ARCENQG QNAME statement in the CA MII QNAME list. The reason for this is that the ARCENQG resource is always issued as an ENQ with a scope of SYSTEMS. In GRS, if there is no RNL entry to change the scope, then the ENQ is always propagated. In CA MII, if you are running with GDIINIT PROCESS=SELECT, then the ARCENQG QNAME statement is required for those requests to be propagated. If you are running PROCESS=ALLSYSTEMS, then the entry is not required. In either case, coding the above entry causes the ENQ to be propagated, which is the desired result.
Similarly, the CA MII QNAME entries for ARCAUDIT, ARCBACK, ARCGPA, ARCGPAL, and ARCUPDT are not required if you were running CA MII with GDIINIT PROCESS=SELECT. PROCESS=SELECT indicates that you want to propagate/convert only those resources that are explicitly specified in MIMQNAME. If you are running PROCESS=ALLSYSTEMS with GDIINIT RESERVES=CONVERT, then the above entries are required to not convert the reserves and propagate global ENQs. Again, in either case, coding the above entries causes the RESERVES not to be converted, which is the desired result.
In addition, note that the entries for SYSDSN and SYSVTOC in the RNL definitions were not explicitly given as RNL specifications in the IBM guide. However, the given DFSMS RNL specifications implied the co-requisite handling of SYSDSN and SYSVTOC in verbal notes. Therefore, we added the GRS RNL specifications and the corresponding CA MII QNAME statements in this example.
Note: For a complete understanding of how CA MII processes an ENQ request, see the CA MII flowchart in the chapter “Advanced Topics”.
|
Copyright © 2014 CA.
All rights reserved.
|
|