Hierarchy
⤷ BC-DB-DB2 (Application Component) DB2 for z/OS
⤷ STU2 (Package) CCMS for DB2 for OS/390
Basic Data
Data Element | DB2CCREORGRECS |
Short Description | DB2/zOS: Number of REORG recommendations by DSNACCOR |
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 | 10 | # REO Recs |
Medium | 14 | # REORG Recom. |
Long | 35 | # REORG recommendations by DSNACCOR |
Heading | 43 | Number of REORG recommendations by DSNACCOR |
Documentation
Definition
Number of REORG recommendations made by stored procedure DSNACCOR for the table space or partition in question.
Job DB02_Refresh looks into DSNACCOR recommendations for the TS in question. If a REORG on the tablespace has not been scheduled for a longer period of time, each run of DB02_Refresh will count this number up.
That's the reason why you should expect higher numbers for LOB and catalog TS, which are reorganized rarely in a 24x7 shop due to availability issues.
This value is a measurement of the frequency of REORG recommendations. This points to tables with a high number of data changes, and you could consider moving tables from multi-table TS to single table TS, switching off SAP-internal buffering, or allocating the TS to another DB2 bufferpool . You could consider exempting some TS from REORG or adjusting DSNACCOR thresholds, for getting less REORG recommendations if you think these REORGs are unnecessary (for instance for volatile tables, that do not grow, or for small table spaces).
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 700 |