SAP ABAP Data Element QQMAXT (iSeries: Maximum 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 | QQMAXT |
| Short Description | iSeries: Maximum 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 | Max. Time |
| Medium | 21 | Maximum Time (ms) |
| Long | 41 | Maximum Time (ms) |
| Heading | 55 | Maximum Time (ms) |
Documentation
Definition
QQMAXT is the execution time in milliseconds of the most expensive execution of a statement as recorded by the memory-resident database monitor.
Note
QQMAXT - like QQMINT - depends on how many records were processed at the times of the various executions of a statement. For example, for one select statement at one time, 10 records are fetched, at another time 1000 records, then the second select execution is naturally slower than the first one, because of the number of fetched records. 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 |
