Previous Topic: Global Data Integrity Facility ProblemsNext Topic: CA MIM Space Performance Considerations

Troubleshooting › Global Data Integrity Facility Problems › ENQ Delays and System Performance Degradation

ENQ Delays and System Performance Degradation

If you experience ENQ delays or bottlenecks on your system, follow these steps:

  1. Examine ENQ/RESERVE activity.

    Verify that you are not converting hardware reserves to global ENQ requests, or propagating SCOPE=SYSTEM or SCOPE=SYSTEMS ENQs against the QNAME recommendations of the vendor. Use the display F MIMGR,DISPLAY COUNTS command to examine ENQ/RESERVE activity. Do not propagate ENQ requests for non‑shared resources.

  2. Refine the QNAME list.

    QNAMEs that should not be managed should be deleted from the QNAME list for customers running with GDIINIT PROCESS=SELECT rather than coding GDIF=NO. Do not code EXEMPT=YES if there are no applicable entries in the EXEMPT list. Also code TRACE=NONE for all QNAMEs, unless there is a specific need to do tracing.

  3. Refine the EXEMPT list.

    Customers running with DEFAULT RESOURCE=GLOBAL JOB=GLOBAL should remove any unnecessary GLOBAL statements. This only increases search time. Similarly, with either RESOURCE=LOCAL OR JOB=LOCAL remove any unnecessary LOCAL statements.