Jerry,
Observe: In the example below, you will note that CONFIGURE.FILE has
no effect on the physical size of the ALPHA file, and the size is
defined by the current modulus.
The modulus can be computed from the size of a dynamic file using
modulus = (totalbytes - 2048)/2048, which will yield "23" for the
BETA file size.
To double check that there was not some sort of sparse creation
algorithm involved, I added 3 small records to the "modulus 23" ALPHA
file, and found that they all appeared in the same group.
ANALYZE.FILE will give you the true modulus (see below).
In the case of ALPHA, deleting records will not contract the file
unless the current modulus is greater than 23.
These examples are on a Solaris system. There is a chance that
Windows behaves differently.
-Rick
:CREATE.FILE ALPHA DYNAMIC
Creating file "ALPHA" as Type 30.
Creating file "D_ALPHA" as Type 3, Modulo 1, Separation 2.
Added "@ID", the default record for RetrieVe, to "D_ALPHA".
:! ls -l ALPHA
total 16
-rw-rw-r-- 1 rick piadm 4096 Mar 9 13:53 DATA.30
-rw-rw-r-- 1 rick piadm 2048 Mar 9 13:53 OVER.30
:CONFIGURE.FILE ALPHA MINIMUM.MODULUS 23
File name = ALPHA
Changing Minimum Modulus from 1 to 23.
File name = ALPHA configured.
:.X2
02 ! ls -l ALPHA
total 16
-rw-rw-r-- 1 rick piadm 4096 Mar 9 13:53 DATA.30
-rw-rw-r-- 1 rick piadm 2048 Mar 9 13:53 OVER.30
:CREATE.FILE BETA DYNAMIC MINIMUM.MODULUS 23
Creating file "BETA" as Type 30.
Creating file "D_BETA" as Type 3, Modulo 1, Separation 2.
Added "@ID", the default record for RetrieVe, to "D_BETA".
:! ls -l BETA
total 112
-rw-rw-r-- 1 rick piadm 49152 Mar 9 13:54 DATA.30
-rw-rw-r-- 1 rick piadm 2048 Mar 9 13:54 OVER.30
:
:ANALYZE.FILE ALPHA
File name .................. ALPHA
Pathname ................... ALPHA
File type .................. DYNAMIC
Hashing Algorithm .......... GENERAL
No. of groups (modulus) .... 1 current ( minimum 23 )
Large record size .......... 1628 bytes
Group size ................. 2048 bytes
Load factors ............... 80% (split), 50% (merge) and 2% (actual)
Total size ................. 6144 bytes
On Mar 9, 2007, at 1:14 PM, Jerry wrote:
Did you mean that UniVerse doesn't have the CONFIGURE.FILE or what?
Because UniVerse has the CONFIGURE.FILE command, the keyword
MINIMUM.MODULUS, and it works immediate without using the IMMEDIATE
key word.
----- Original Message ----- From: "Richard Nuckolls"
<[EMAIL PROTECTED]>
To: <u2-users@listserver.u2ug.org>
Sent: Friday, March 09, 2007 2:35 PM
Subject: Spam:Re: [U2] Dynamic files, big transactions
CONFIGURE.FILE MINIMUM.MODULUS ... (in the Prime/PI Open version)
would accept a keyword of IMMEDIATE to force the splitting of
groups. Universe lacks this option, so you should specify
MINIMUM.MODULUS at the time that you create the part file.
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
