
FUP Commands
File Utility Program (FUP) Reference Manual—523323-014
2-153
RELOAD Guidelines
To monitor the status of a reload operation, use the STATUS command.
To temporarily stop the reload, use the SUSPEND command.
Access to
filename
by an application (during the reload) requires shared access.
The reload operation on an audited file generates audit records that describe the
movement of data within the file. The audit record total from a file can triple the file
length (discounting free space).
A reload operation can degrade system performance. To control the processor time
used by the reload, use the RATE parameter. Any percentage below 100 prevents
the reload from monopolizing the processor and its resources.
To prevent system performance degradation, do one of:
Increase the TMF audit-trail file configuration before you use FUP RELOAD.
Reduce the rate of audit-trail generation by decreasing the RATE percentage in
the RELOAD command.
If you are restarting a reload operation and do not specify new rate and slack
values, FUP uses the values from the previous reload operation.
To reload all of a key-partitioned file’s partitions, you must reload each partition
separately. If the primary partition is the only one specified in the RELOAD
command, it is the only partition that is reloaded.
An online file reload can generate a large amount of audit-trail information (in a
short amount of time) for TMF-audited files or tables. The amount of audit
information generated increases if you concurrently run multiple reloads.
The reload operation creates and maintains the file ZZRELOAD.ZZRELOAD,
which contains status information for the current and past reload operations. There
is one ZZRELOAD file per volume, created the first time a reload is run on it.
The reload operation requires a small amount of disk space to reorganize the
specified file—even if the result of the operation is a smaller file. A reload operation
fails if insufficient disk space is available on the volume for RELOAD (ORSERV) to
perform the file reorganization.
When you run RELOAD on an SQL partitioned file concurrent to the split of
another partition, it terminates abnormally (ABENDs) with error 60. FUP treats this
error as a suspended operation and displays this message and the suspended
information in the STATUS command:
ERROR:RELOAD SUSPENDED DUE TO DDL OPERATION
The user running FUP must have remote access to any system, which is implicitly
referenced by the ANSI name used in the FUP command. For example, if the ANSI
name is 'TABLE C.S.T', the user must have access to any node on which partitions
of table C.S.T reside, and so on.