SAP ABAP Data Element QQMINT (iSeries: Minimum Time (Database Monitor))
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DB-DB4 (Application Component) DB2 for AS/400
⤷
STU4 (Package) CCMS / AS/400
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB4 (Application Component) DB2 for AS/400⤷
STU4 (Package) CCMS / AS/400
Basic Data
| Data Element | QQMINT |
| Short Description | iSeries: Minimum Time (Database Monitor) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | QQDEC150 | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 15 | |
| Decimal Places | 0 | |
| Output Length | 19 | |
| 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 | 11 | Min Time |
| Medium | 21 | Minimum Time (ms) |
| Long | 41 | Minimum Time (ms) |
| Heading | 55 | Minimum Time (ms) |
Documentation
Definition
QQMINT is the execution time in milliseconds of the least expensive execution of a statement as recorded by the memory-resident database monitor.
Note
QQMINT - like QQMAXT - depends on how many records were processed at the time of the various executions of a statement. For example, whilst at one time 10 records are fetched for an SQL statement, at another time 1000 records are fetched. The first SELECT is naturally faster than the second one, because of the number of records fetched. These differences can occur because of different host variables used in the various statement executions or because of the number of records in the table(s) accessed.
History
| Last changed by/on | SAP | 20070813 |
| SAP Release Created in |
