Release Overview
Version 6.0

Larger pre-allocate and extension factors

Vision 5 supports larger pre-allocate and extension factors than prior versions of Vision. The limit on both factors is now 2,097,152--1 GB of 512-byte blocks. The higher limits may be used anywhere that a pre-allocate or extension factor is specified for a Vision 5 file.

Index pre-allocate and extension factors as a percentage of the factors applied to the data segment

In Vision 4 and 5 files, the index data contained in the index segments is often much smaller than the record data contained in the data segments. Consequently, a large pre-allocate or extension factor typically allocates many more index blocks than are needed. This can be undesirable, especially if disk space is tight.

A new configuration variable, V_INDEX_BLOCK_PERCENT, allows you to specify index pre-allocate and extension factors as a percentage of the factors applied to the data segment. This allows you to control the number of index blocks created whenever an allocation is performed. For more information, see the entry for V_INDEX_BLOCK_PERCENT in Appendix H of Book 4, ACUCOBOL-GT Appendices.

If you use I$IO, you may be interested to know that the PRE-ALLOCATION-AMOUNT and EXTENSION-AMOUNT data items in sample/def/filesys.def have changed size due to the larger values allowed.

If you use C$REDIRECT you may be interested to know that the HANDLER-PRE-ALLOCATE-AMOUNT and HANDLER-EXTENSION-AMOUNT data items in sample/def/handler.cpy have changed size due to the larger values allowed.

Specifying a pre-allocation factor with vutil when rebuilding a file

The new "-p pre_factor" option to the "vutil -rebuild" command allows you to specify a pre-allocation factor for a file that you are rebuilding. See section 3.3.3, "Rebuilding Files," in Book 1, ACUCOBOL-GT User's Guide.

© 1988-2003 Acucorp, Inc. All rights reserved.