Why is There a Long Chain of Enqueues/Dequeues for a CA View Database?
CA View issues ENQs and RESERVEs as necessary, to maintain the integrity of its data sets.
If a system-integrity product (like GRS) is in use, accommodations must be made for a new CA View database.
As RESERVES are issued against both a database's first index extent (....SARDBASE.I0000001) and first data extent (....SARDBASE.D0000001), a review of local configurations is required.
The primary ENQ (QNAME=SARSTC) is used by the SARSTC archival task, to ensure that only one archival task is using a specific database.
The ENQ is defined as SYSTEMS which will be propagated to all LPARs in a PLEX. This queue name need not be defined to a system-integrity product.
A secondary ENQ (QNAME=SARPAC) is used by the tape consolidation utility SARPAC. This is also defined as SYSTEMS, and need not be defined to a system-integrity product.
The RESERVE issued by CA View is normally short-lived, but it can cause deadlock conditions unless properly defined.
The general recommendation is to convert any RESERVEs to global ENQs.
Conversion to a global ENQ can be done, for SARUPD, using:
. RNLDEF RNL(CON) TYPE(GENERIC) QNAME(SARUPD)