Executing CREWSRTR and the job hangs with a volume enqueue. How do we resolve?

Products

• CREWS Catalog Recovery

Issue/Introduction

Executing CREWSRTR and the job hangs with a volume enqueue. How do we resolve? Do we have a sample GRS or MIM enqueue conversion statement to resolve enqueues for CREWSRTR?

Environment

z/OS

Resolution

The CA CREWS User Guide Chapter 11 describes the enqueue requirements but does not provide sample CA MIM or IBM GRS control statements to assist in converting the Volume Enqueue to a Global Enqueue.  

For CA MIM

QNAME=CREWSRTR,GDIF=YES,SCOPE=SYSTEMS,RESERVES=CONVERT

For IBM GRS

RNLDEF RNL (CON) TYPE (GENERIC) QNAME (CREWSRTR)

RNLDEF RNL (CON) TYPE (GENERIC) QNAME (SYSIGGV2) 
RNLDEF RNL (CON) TYPE (GENERIC) QNAME (SYSZVVDS) 
RNLDEF RNL (CON) TYPE (GENERIC) QNAME (SYSVTOC) 

  

Additional Information

CA CREWS User Guide Chapter 11

Since CREWSRTR issues a hardware RESERVE on the volume on which the ICF Catalog resides, it is strongly recommended that MIM, GSR or a comparable product be used to convert the hardware reserve to an ENQ. The MAJOR QNAME used is SYSIGGV2 and the MINOR QNAME is the dataset name pointed to by the CATALOG DD statement. If you are reorganizing to a new volser then an additional RESERVE will be issued for the new device as well. The MAJOR QNAME is CREWSRTR and the MINOR name is the dataset name pointed to by the CATALOG DD statement. As with above, it is strongly recommended that MIM, GSR or a comparable product be used to convert the hardware reserve to an ENQ. 

 

Also, see II14297: CATALOG AND GRS CONFIGURATIONS" from IBM