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 | DB2CCRROWS |
| Short Description | REORG TS/IX: Number of active pages |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 11 | |
| 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 | 7 | # pages |
| Medium | 15 | Number of pages |
| Long | 22 | Number of active pages |
| Heading | 22 | Number of active pages |
Documentation
Definition
Beginning with DB2 V7.1, SAP utilizes a stored procedure named DSNACCOR which recommends running a utility based upon data in the real-time statistic tables. The recommendation for a REORG on a table- or indexspace is based on a complex calculation, which is detailed in DB2 UDB for OS/390 and z/OS V7 Utility Guide and Reference.
This value is not used by DSNACCOR itself, but SAP suppresses Alerts that are generated on small tables, to reduce the number of REORG recommendations. As long as the recommendation was not given based on number of unclustered inserts, overflow records or extents or due to advisory REORG status, then the number of active pages in the table space/index or partition is compared to this threshold. If it is less than this value, a recommendation of DSNACCOR to run REORG on the tablespace/index is suppressed by SAP.
The default is 0, to simulate the behaviour in the past. A good value would be 20-30, but will depend very much on your environment and your need for reducing the number of REORG alerts. The value shouldn't be too high, or fragmentation within small TS resp. possible space savings will remain undetected.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 700 |
