File Utility Programming (FUP) Reference Manual

FUP Commands
File Utility Program (FUP) Reference Manual—523323-015
2-145
LOADALTFILE Guidelines
MAX num-records
specifies the number of records to be read from primary-filename. The
default is 10,000,000. Specify num-records as a whole number ranging from
0 through (512000000 * 2048) - 1. To determine the size of the scratch file that
is used by the SORT process, FUP multiplies num-records by the number of
alternate keys associated with key-file-number. The num-records value
should be equal to or greater than the actual number of records in the primary
file.
SCRATCH scratch-filename
specifies a file or volume to use for temporary storage while sorting. If you omit
this option, FUP uses a scratch file on the default volume.
DSLACK percentage
ISLACK percentage
SLACK percentage
specify the minimum percentage of space to reserve in the index and data
blocks for future insertions. If space is not available when an insertion is made,
a block split occurs.
LOADALTFILE Guidelines

To perform a LOADALTFILE operation, you must have read and write access to
the alternate-key files and read access to the primary file.

LOADALTFILE ignores any NO UPDATE specifications.
LOADALTFILE honors any NULL specification defined for a key field, but an
alternate-key record is not generated for a field consisting entirely of null
characters (if such a null character was defined).

A sort operation is performed when you execute LOADALTFILE. The primary file is
read sequentially according to its primary-key field. The alternate-key records are
generated and written to the SORT process for each record read from the primary
file. The sorted records are read from the SORT process and loaded into the
indicated alternate-key file after the sort is complete. Disk space for the sort
scratch file must exist during the sorting phase.

You can use a SORT DEFINE with the LOADALTFILE command. You must define
it before you start FUP. For more information, see the FastSort Manual.

If the attributes of the alternate-key file are incorrect (for example, insufficient
record length, key offset not zero, or not a key-sequenced file), LOADALTFILE fails
and displays:
ERROR - ALT FILE IS INCOMPATIBLE WITH ALT KEYS
Note. For a complete description of these options, see LOAD on page 2-136.