I am experiencing ACF2 database contention problems in a shared DASD environment. What are the most common causes of ACF2 database contention problems?
ACF2 database contention problems in a shared DASD environment can be a result of database volume placement or not excluding ACF2 properly with an enqueue-controlling product such as CA MIM or GRS.
To prevent potential ACF2 Database contention problems the following should be done.
Sites using Unicenter CA-MIM and any other enqueue-controlling product should specify the following ENQ resources in their exclude list:
- Exclude the CA ACF2 data set names from the SYSDSN
ENQUEUE so that CA ACF2 can have the databases as
DISP=OLD on more than one CPU.
- Exclude the CA ACF2?s name from the SYSVSAM
- Exclude CA ACF2?s major name, ACFVSAM, to let CA
ACF2 serialize its function in the system, not the entire ring.
Please consult the CA MIM or GRS documentation for details on the syntax for the exclude statements.
CA MIM NOTE: If you are running CA MIM in place of GRS, add the NO-SMC attribute to the MIM address space logonid. This will ensure that concurrent security requests in the MIM address space, which require access to the CA ACF2 databases, do not get single threaded and result in possible system suspends.
Database Volume Placement
In a shared ACF2 database environment it is recommended that the ACF2 databases should be the only VSAM files on the volume because of potential contention and/or performance problems.
Ensure that the CAACF2 databases are in their own User Catalog (USERCAT). The USERCAT should not contain any other data sets. The USERCAT should not be on the same device as any of the CA ACF2 databases.
For performance reasons, the CA ACF2 clusters should be allocated on a DASD device with minimal I/O activity. In addition, the device should not contain any z/OS master or user catalogs.
The databases should not be on volumes that are heavily used by any other system tasks, or on any volume subject to extensive I/O. The same consideration should also be given to the placement of the alternate databases. Additionally, do not place the alternate databases on the same volumes as the primary databases.
NOTE: These are the most common causes of database contention problems. If all of the above are verified and you are still experiencing a problem the following documentation is
- Console log showing any errors, abends or messages related to the contention/ENQUEUE problem.
- Dump of the CA MIM or GRS address space.
- Dump of the address space holding the database ENQUEUE.