Software Distributor Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (5900-2561, March 2013)

1.4.4 Session Files
Before any SD-UX task starts, the system automatically saves the current command options, source
information, software selections, target selections, etc., into a session file. You can then re-use this
session information at a later time, even if the command fails.
Session information is saved in the $HOME/.sw/sessions/ directory as command.last in
which command is the name of the command. Each time you save a session file, it overwrites the
previously stored one. (To save multiple session files, you can rename each session file after you
invoke the command.)
To re-use the automatically saved session file, invoke the command with the -S swcommand.last
argument. For example:
swinstall -S swinstall.last
If you want to save a session file to somewhere other than the default sessions directory, use the
-C session_file argument and supply your own absolute path to the file you wish to save. If
you do not specify a directory, the default location for the session file is $HOME/.sw/sessions/.
To re-execute a session from a command line, specify the session file as the argument for the -S
session_file option.
Note that when you re-execute a session file, the session file values take precedence over values
in the system defaults file or personal defaults file. Likewise, any command line options or parameters
that you specify when you invoke the command take precedence over the values in the session
file.
Here is a sample a session file. It uses the same syntax as the defaults files:
# swinstall session file
#
# Filename /users/fred/.sw/sessions/swinstall.last
# Date saved 05/26/01 15:59:41 MDT
swinstall.allow_downdate = true
swinstall.allow_incompatible = false
swinstall.allow_multiple_versions = false
swinstall.autoreboot = false
swinstall.autorecover_product = false
swinstall.compress_files = false
swinstall.create_target_path = true
...
(A typical swinstall session file has approximately 70 lines.)
1.4 Working from the Command Line 39