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 | DB2PARTEXT |
| Short Description | Extension or Partition (non-partitioned TS) number |
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 | Ext/Part |
| Medium | 19 | Extension/Partition |
| Long | 26 | Extension/Partition number |
| Heading | 50 | Extension or Partition (non-partitioned TS) number |
Documentation
Definition
SAP by default uses DB2-managed data sets. When the data set is created, DB2 always allocates a primary allocation space on a volume that has space available and is specified in the DB2 storage group.
DB2 extends data sets when:
- The requested space exceeds the remaining space
- 10 percent of the smaller allocation space (but not over 10 allocation units such as tracks or cylinders) exceeds the remaining space
This new space is allocated in extents of a data set. Any new extent always gets a secondary allocation space.
Extending nonpartitioned spaces:
For a nonpartitioned table space or an index space, DB2 defines the first piece of the page set starting with a primary allocation space, and extends that piece with secondary allocation spaces, which are called extents for the data set. When the end of the first piece is reached, DB2 defines a new piece (which is a new data set) and extends to that new piece starting with a primary allocation space. This is called an extension of a nonpartitioned space.
These extensions can be identified by a sixth qualifier in the dataset name that is different from A001, i.e. A002 for the first extension, A003 for the second extension and so on.
Extending partitioned spaces:
For a partitioned table space or an index space, each partition is a data set, that can be identified by the sixth qualifier in the dataset name. So the sixth qualifier is A001 for the first partition, A002 for the second partition, A003 for the third partition and so on.
DB2 defines each partition with the primary allocation space and extends each partition's data set with secondary allocation space, as needed. Therefore, partitioned spaces have only extents and no extensions.
This value is:
- The partition number for partitioned table spaces.
- The extension number for non-partitioned tablespaces. This is also the reason, why this value is different from the value in column SYSIBM.SYSTABLEPART(Partition), which is by definition 0 for non-partitioned tablespaces.
This means, that this column is not suited for detecting if the table/index space is partitioned! Please use column PARTITIONS for this purpose.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 700 |
