Software Distributor Administration Guide for HP-UX 11i

Reliability and Performance
Retry Command
Chapter 8244
Retry Command
SD-UX supports options that facilitate retrying operations that have
failed. These can be used in conjunction with the checkpointing features
or can start the task from the beginning.
Each execution of a command records all of the target, software, and
option selections automatically in a session file,
command .last. You can
also save the session information to a different file using the GUI. The
session files are stored in the directory $HOME/.sw/sessions. The entire
command can be retried by recalling the session in the GUI or by
re-executing the task:
command -S command .last
When a task is retried, any fileset that is up to date (has the same
product and filesets revisions as available or installed and is not in the
transient or corrupt state) will not attempt to be reinstalled (the default
behavior), and all other filesets will be retried. This behavior can be
overridden, forcing the retry to start at the beginning of all files, by
setting reinstall=true from either your option setting or the CLI.
If the reinstall_files option is set to true, all files in that fileset are
retransferred. However, although preinstall and postinstall scripts for
filesets that are being installed are executed normally, the file transfer
for up to date files can be avoided by leaving the reinstall_files
option equal to false (the default).
When the reinstall_files option is false, the user can also control
which attributes are checked in order to determine if the fileset is
already installed or available. If the reinstall_files_use_cksum
option is set to true, the size, mtime, and cksum attributes are checked.
If the reinstall_files_use_cksum option is false, then only the size
and mtime are checked. Checking the cksum attribute is more time
consuming but more reliable. The size and mtime checks are very fast.
The user can see which files were actually installed or copied and which
were skipped due to being already up to date by setting the loglevel
option to 2.