
FUP Overview
File Utility Program (FUP) Reference Manual—523323-014
1-23
Moving Format 1 File Contents to Format 2
When you specify Format 0, the system decides the format of the file based on other
file attributes. The system chooses Format 2 when the block size is over 4 KB or when
a partition size is over 2 GB minus 1 KB. For unstructured, relative, and entry-
sequenced files, the system chooses Format 2 when the total file size is 4 GB or more.
By default, Format 1 is assumed.
The FUP INFO command provides the value of the file format for existing files.
Moving Format 1 File Contents to Format 2
You cannot convert an existing Format 1 file partition to Format 2. Any attempt to alter
the max extents of the Format 1 file, such that the partition exceeds 2 GB minus 1 MB,
is rejected.
To put the content of a Format 1 file into a Format 2 file:
1. Create a Format 2 file.
2. Use the LOAD command or a comparable operation to move the contents of the
Format 1 file into the Format 2 file.
You cannot update the Format 1 file during such a LOAD operation, and all access
must be shut down to switch to the new 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.
Table 1-1. File Format Codes
Format
Code
Maximum Block
Size (in Bytes)
Maximum Record Size (in
Bytes)
Maximum Partition Size
(in Bytes)
0
4096
Determined by system
Determined by system
1
4096
Block size - 34 (key sequenced)
Block size - 24 (relative and
entry sequenced)
2 GB - 1 KB
2
4096
Block size - 56 (key sequenced)
Block size - 48 (relative)
Block size - 48 (entry
sequenced)
1024 GB
Note.
FUP supports Format 2 SQL partitions in the G06.13 and later RVUs. FUP supports
fallback from G06.13 to as far back as G06.03. If you are running an RVU prior to G06.03, you
cannot fall back to your previous RVU.
FUP commands display error 584 when they encounter Format 2 SQL partitions on a system
that has fallen back from G06.13 to an earlier RVU. FUP continues to process the remaining
files.