The MODIFY-RECORD-POPULATION statement can be used to change the maximum record population (DBTT) of a record type.
MODIFY-RECORD-POPULATION | ||||||||||||||||
| ||||||||||||||||
RECORD-NAME = <record-name>
Name of the record type for which the record population is to be changed.
RECORD-POPULATION = <integer 1..2147483647>
The number of permissible DBTT entries for the record type is equivalent to the specified value.
RECORD-POPULATION = *RELATIVE (...)
The new size of the DBTT is calculated from the old size and the specified difference (which may be a positive or negative value), but cannot be less than the size attained by specifying MINIMUM.
DIFFERENCE = <integer -2147483647..2147483647>
Difference with respect to the old DBTT size; as a number of DBTT entries.
RECORD-POPULATION = *MINIMUM
The DBTT of the record type is reduced to the smallest possible value.
Entries that are invalid for databases with a 2-kbyte format cannot be detected via SDF if the entered values lie within the ranges specified above.
Since these databases are subject to additional checks, the old limits are still applicable to them.
Since the DBTT always occupies all pages that are reserved for it entirely, it is conceivable that after a BREORG run in which an increase is requested, more records can be stored than were actually specified in the statement. In the reverse case, if you use the statement to deallocate fewer DBTT entries than are actually contained in a DBTT page of the specified record type, then the maximum permissible number of records in this record type stays the same.
Since entire pages are always reserved for the DBTT, the number of desired entries is rounded up to full pages.
However, if the maximum RSQ is exceeded in the process, the number is rounded down to full DBTT pages.
The SSIA-RECORD may only be modified under the PRIVACY-AND-IQF-SCHEMA.
When a database is reorganized, DBTT extents may be created independently of the activation of online DBTT extension. An increase in the size of the DBTT due to BREORG is implemented in DBCOM and DBDIR by enlarging the existing DBTT. In the user realm, the DBTT is enlarged by BREORG by means of DBTT extents if the target DBTT has a total size greater than 128 PAM pages. If the target DBTT is smaller than or equal to 128 PAM pages then BREORG always implements it as a DBTT base, i.e. as a single unit. The corresponding messages inform you of the results of increases or reductions in the size of DBTTs.
The last DBTT extent is also always present in full. The number of required entries is not just rounded up to full pages, but to full DBTT extents.
Execution messages
On executing a MODIFY-RECORD-POPULATION statement, the results of the DBTT reorganization of the record type are output as follows:
| |
| |
|
|
|
|
|
|
|
|
|
|
| |
record-name
Name of the modified record type
area ref - page no
Act-key of the first or last DBTT page
number extents
New number of DBTT extents
number pages
New number of DBTT pages
number entries
New number of records