Fujitsu UDS/SQL V2.5 Manual Do Utilizador
![Fujitsu](https://files.manualsbrain.com/attachments/6c4642b33d2edbd09f94719c20a133aa0e862902/common/fit/150/50/80a45702a21fefb1823bce6851e87db450dccf7792cb572ebc8a90330a68/brand_logo.png)
SSL
Population
U929-J-Z125-9-76
137
D
ok
us
c
h
abl
on
en
1
9x
24 V
e
rs
ion
7
.3
us
f
ü
r F
ram
eM
ak
er
V
7
.x
v
o
m
1
4.
02
.2
00
7
©
c
o
gni
tas
Gm
b
H
20
01-
20
07
24
. Ok
tobe
r 20
07
S
ta
nd
0
8:
58
.5
5
P
fa
d:
G
:\
v
og
t\
fs
c
\ud
s
\M
anu
al
e
\e
n\
ud
s
e
nt
_e\
u
ds
ent
.k
0
5
Note, however, that UDS/SQL always creates only as many DBTT pages as required for the
DBTT and that, depending on the database page length, a maximum of 2
DBTT and that, depending on the database page length, a maximum of 2
24
-1 or
2
24
- 2
16
- 1 (=16711679) or 2
31
-1 entries per DBTT can be administered. Since a DBTT
base can only be created in whole pages and a DBTT extent only in DBTT extent size (128
PAM pages), an excess amount is usually created if the maximum values are specified. This
excess amount is not used.
PAM pages), an excess amount is usually created if the maximum values are specified. This
excess amount is not used.
The DBTT can be extended by means of the BREORG utility routine (see the "
" manual, BREORG).
By default, UDS/SQL reserves one page for a DBTT.
If a secondary key has been defined for a record type for conversion by a hash routine, the
size specification for the DBTT also affects the initial size of the hash area (see the section
size specification for the DBTT also affects the initial size of the hash area (see the section
).