SAP ABAP Data Element DB2BACHRF (Number of Unsuccessful Synchronous Hiperpool Reads)
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
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 | DB2BACHRF |
| Short Description | Number of Unsuccessful Synchronous Hiperpool Reads |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DB2INT4U | |
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | HP read un |
| Medium | 18 | HPool reads unsuc |
| Long | 28 | Unsuccessful hiperpool reads |
| Heading | 0 |
Documentation
Definition
An unsuccessful read occurs when a requested page was found in the hiperpool, but its content was discarded by MVS. For hiperpools defined as CASTOUT=YES, the written data can be discarded by MVS if the hiperpool usage is low or if the expanded memory is not large enough to back the hiperpool.
If this number is large for CASTOUT=YES hiperpools, reduce the size of the hiperpool.
For hiperpools defined as CASTOUT=NO, an unsuccessful read can only happen when the backing expanded storage page was explicitly reconfigured out of the system.
History
| Last changed by/on | SAP | 20070813 |
| SAP Release Created in |
