Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB2 (Application Component) DB2 for z/OS⤷
STU2 (Package) CCMS for DB2 for OS/390
Basic Data
| Data Element | DB2XMIAP |
| Short Description | Number of times RID list processing is used |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DB2DEC19V | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 19 | |
| Decimal Places | 0 | |
| Output Length | 26 | |
| 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 | 15 | Used |
| Long | 20 | RID list proc. used |
| Heading | 0 |
Documentation
Definition
During RID (Record ID) list processing, DB2 uses
an index to produce a list of candidate RIDs, which is called a RID
list. The RID list can be sorted and intersected (anded) or unioned
(ored) with other RID lists before actually accessing the data pages.
RID list processing is used for a single index (index access with list
prefetch ) or for multiple indexes (multiple index access), which is
when the anding and oring of RID lists occurs. This field is
incremented when RID list processing is used for index access with list
prefetch and/or for multiple index access. For multiple index access,
if a final RID list is obtained through anding and oring of RID lists,
the counter is incremented once, even if RIDs from all indexes in the
multiple index access were not used.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
