FUP Commands
File Utility Program (FUP) Reference Manual—523323-014
2-161
RESTART Guidelines
RESTART Guidelines
ï‚·
FUP (DUP) updates the restart file periodically. This causes a RESTART operation
to start from the last update, which is not necessarily from the last record written.
ï‚·
The RESTART operation fails if any of these conditions exist:
ï‚°
The last modified time of the source file has changed.
ï‚°
A file with the same name as restart-filename exists on the destination
disk for the DUP operation.
ï‚·
FUP does not verify if the security, ownership, or other attributes of the source file
have changed since the last modified time of the file. The file attributes appear in
the file label of the source file.
ï‚·
During a RESTART operation, FUP makes additional updates to the restart file to
record its progress. If the RESTART operation fails, a subsequent RESTART
operation can continue from the point where the failed operation stopped.
ï‚·
The RESTART file is purged when the DUP[LICATE] process finishes.
ï‚·
The restart file created by H01 version of FUP cannot be used with H02 version of
FUP and vice versa.
RESTART Examples
ï‚·
This example assumes that the DUP operation from the first command fails. The
RESTART command restarts the DUP operation.
-DUP FILE1, FILE2, RESTARTABLE
-RESTART
If a RESTARTABLE DUP operation fails and you issue a RESTART command,
FUP always echoes the original DUP command in uppercase.
A restart-filename is not included in the RESTARTABLE option of the DUP
command, so FUP searches for the ZZRSTART file on the current subvolume for
the information it needs to perform the RESTART operation.
ï‚·
To include a restart-filename with the RESTARTABLE DUP command:
-DUP OLDFILE, NEWFILE, RESTARTABLE RSFILE
.
.
-RESTART RSFILE
If the DUP operation fails, the RESTART command must specify the name of the
RSFILE to request FUP to use the information contained in the unstructured file
(file code 855) RSFILE for the RESTART operation.
To Next Page
Loading...
Need help?
General