File Utility Programming (FUP) Reference Manual

FUP Overview
File Utility Program (FUP) Reference Manual—523323-015
1-24
Inserting Partitions in Enscribe Key-Sequenced File
You can create an equivalent Format 2 file for most Format 1 files. A Format 1 file with
a record size within 56 bytes of the block size (48 if not key-sequenced) cannot have a
Format 2 file with the same size created for it. You can use a larger block size for the
Format 2 file unless the Format 1 file already has a 4096 byte blocksize.
You likely need to change existing applications to access Format 2 files over 4 GB in
size that are not key-sequenced. These files require the use of a 64-bit primary key,
and system interfaces preceding G06.00 or D46.00 support only 32-bit primary keys.
Applications are unlikely to require any changes to access key-sequenced Format 2
files.
Except for key-sequenced files, all partitions of a file must have the same format
(Format 1 or Format 2). You cannot create a key-sequenced file with a mix of partition
formats. However, you can replace the partitions one at a time with equivalent Format
2 partitions if the block and record sizes are the same for all partitions.
You should convert a key-sequenced partition to Format 2 when it approaches its
capacity limit:
1. Create a new Format 2 replacement partition on a different volume.
2. Load the data into the new partition from the Format 1 partition.
3. Change the file partition information to point to the new Format 2 partition instead
of the Format 1 partition.
If Format 2 files are created on a system running D46.00, G06.00, or subsequent
RVUs, fallback to an RVU prior to D46.00 or G06.00 precludes access to the contents
of those files. Access to Format 2 files in an Expand network from RVUs before D46.00
or G06.00 will not be possible.
Inserting Partitions in Enscribe Key-Sequenced File
Provided the following conditions are met, FUP can insert a new secondary partition
into an enscribe key-sequenced file without disturbing the existing loaded data:
1. Ensure that the primary partition does not contain any data, and the first secondary
partition has a null partition key value.
2. Since data is not moved, the file must not contain any records that are based on
their key values, and logically belong to the new partition.
3. For a non-audited file, step 1 and 2 must be followed while the file is open.
However, non-audited file must be closed and re-opened for the new partition to be
used.
4. For an audited file, the file must be closed first, the audit flag must be turned off,
step 1 and 2 must be followed, and then the audit flag must be turned back on.
Now, the file can be re-opened by the application.