The number of suspensions due to false contention. This happens when different resource names hash to the same entry in the coupling facility lock table. This causes MVS XES to detect contention on the hash class, however, when MVS XES determines that there is no real conflict on the resource, the contention is called false.
z/OS 1.2 added a new data sharing function to dynamically convert CF requests from sync to async based on heuristics that indicate which mode of invocation is more efficient. One side effect is that when these heuristics kick in to convert an IRLM Lock request from sync to async, the instrumentation feedback is identical to the feedback that z/OS gives DB2 for false contention. Therefore, this counter (QTGSFLSE) may no longer be accurate. False contention may be over-reported, sometimes significantly, especially when CFs are located long distances from the host processors.