Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB2 (Application Component) DB2 for z/OS⤷
STU3 (Package) Development Class for Database Monitor
Basic Data
| Data Element | DB2HPFAIL |
| Short Description | Number of Hiperpool Failures |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 20 | |
| 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 | 18 | Hiperpool failures |
| Long | 20 | Hiperpool failures |
| Heading | 0 |
Documentation
Definition
The number of hiperpool failures is defined as the sum
QBSTHRF + QBSTHWF + QBSTARF + QBSTAWF
where
QBSTHRF:
Read request failed because the backing expanded storage page was stolen by the system.
An unsuccessful read occurs when a requested page was found in the hiperpool, but its content was discatded by MVS. This count does not include pages moved by the asynchronous data mover facility. For hiperpools defined as CASTOUT=YES, the written data can be discarded by MVS if the hiperpool usage was low or if the expanded memory was not large enough to back 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.
QBSTHWF:
Number of pages for which a synchronous or asynchronous write request failed because of a shortage of expanded storage. In other words, no backing expanded storage page could be allocated.
This count does not include pages moved by the asynchronous data mover facility
QBSTARF:
Number of pages for which a read request, using the asynchronous data mover facility, failed because the backing expanded storage was stolen or some other error occurred.
For hiperpools defined as CASTOUT=YES, the written data can be discarded by the system because the hiperpool usage was low or the expanded memory was not large enough to back the hiperpool. For hiperpools defined as CASTOUT=NO, backing expanded pages are stolen only when they are explicitly reconfigured out of the system.
QBSTAWF:
Number of pages for which a write request, using the asynchronous data mover facility, failed because the backing expanded storage was stolen or some other error occurred.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
