Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB2 (Application Component) DB2 for z/OS⤷
STU3 (Package) Development Class for Database Monitor
Basic Data
| Data Element | DB2TLOPRAT |
| Short Description | Locking optimization rate |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DB2CHAR10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 0 | |
| Long | 37 | Locking optimization rate |
| Heading | 0 |
Documentation
Definition
This ratio shows how many lock requests are not propagated to XES and coupling facility because of global locking optimizations.
It is computed as
100 - (100 * (QTGSLSLM - QTGSLPLK) / QTXALOCK)
where
QTGSLSLM:
The number of lock requests propagated to MVS XES synchronously (that is, under the user's execution unit).
This count includes both L-locks and P-locks. It is not incremented if the request is suspended before going to XES.
QTGSLPLK:
The number of lock requests for P-locks.
QTXALOCK:
Lock request count.
Note that z/OS 1.2 introduces a heuristic function that dynamically converts coupling facility requests from synchronous to asynchronous. If such conversions occur, QTGSLSLM does not contain the lock requests, which are converted to asynchronous. As a consequence the locking optimization rate is not correct in this case.
History
| Last changed by/on | SAP | 20070813 |
| SAP Release Created in | 700 |
