NAME
install++ - configures and installs software
SYNOPSIS
install++ -s path [-efilmoprvx][-c file1][-C file2][-a|-u|-d|-k] -n file3
install++ -s path [-efilmoprvx][-c file1][-C file2][-a|-u|-d|-k] name
install++ -s path [-efilmoprvx][-c file1][-C file2][-a|-u|-d|-k] [-n
file3] name ...
DESCRIPTION
INSTALL++ configures and installs software to a node or nodes. It
determines the configuration of software to be installed on the target
node(s) either by:
o using a pre-existing configuration file
o creating a new configuration file interactively.
There is no specified order for arguments and/or options, with the
exception that the argument(s) 'name ...' , if present, must come at the
very end of the command line. The comannd line must contain the -s option
and at least one of the configuration options -a, -c, -C, or -u.
After determining the software configuration to be installed, the program
installs the desired software on the target node(s). In the process, it
creates or updates a 'baseline' file on each target node, containing a
history of installations. on that node.
OPTIONS
-a installs on the target the latest default version of all
available products in the Authorized Area. Incompatible with
-c, -C, -d, -k, or -u options.
-c configuration_file
installs software according to the contents of a configuration
file at pathname configuration_file. There can be multiple
instances of this option with configuration files for different
products. Incompatible with -a or -u options.
-C file_list
installs software according to the contents of multiple
configuration files (for example, one configuration file per
product) as described in the '-c file' option above. The list
of configuration files to be used is contained in the file at
pathname file_list, one pathname per line. There can be
multiple instances of this option with different file lists for
different sets of products. Incompatible with -a or -u
options.
-d runs the installation in noninteractive mode. If the
configuration file contains options to a product for which the
answers are unspecified (marked by "N/A" in the file), the
answers are extracted from the default values in the product's
release index. Incompatible with -a or -u options.
-e checks that all files required for an installation are present
in the Authorized Area before installation begins. In a
multiple node installation, this test is done on a target-by-
target basis.
-f writes out the new baseline file after all products are
installed to the target node; default is to update the baseline
file after each individual product is installed.
-i assumes that the total block size of all the objects to be
installed is less than the available disk space on the target;
therefore, install++ does no size checks. By default, the tool
checks for available disk space and warns the user if it is not
sufficient. This option is useful if you are replacing one
version of a product with a more recent version, since most of
the space required by the new objects is available after
deletion of the old ones. We recommend that you use this option
when installing software in batch mode on an unattended node,
for example, in an overnight installation.
-k runs the installation in noninteractive mode. However, if the
configuration file contains options for which the answers are
unspecified (marked by "N/A" in the file), the queries about
those options are presented to the user. Incompatible with -a
or -u options.
-l In the case where the source node and the target node are the
same, installs by using hard links from the destination paths
into the Authorized Area instead of duplicating the files.
-m ignores object customization; supports a user who has
customized software after installation by changing or deleting
some of the objects belonging to a product, and now wants to
get back the files that were deleted without overwriting the
files that were changed.
If this option is not used, installing software in the above
situation does not cause the "missing" objects to be recopied.
With this option, they are recopied.
-n list specifies the pathname of a file containing a list of node
entry directories (for example //pickle), or subdirectories
(for example /pickle/disk1), that are to be the targets of the
installation. List one nodename per line. Either this argument
or the //node1 [..nodeN] argument must be given. More than one
instance of this argument may be given.
name ...
are the names of one or more node entry directories, or
subdirectories, which are to be the targets of the
installation, for example //picnic or //picnic/disk2. Either
this argument or the -n list argument must be given. If this
argument is given, it must be the last item on the command
line.
-o installs to all targets, possibly multiple times; by default,
install++ installs to each target path only once during a
single invocation of the tool. With this option, you can ensure
successful installation of software during an unattended
installation over a large, heavily used network by naming each
target twice.
-p purges all but the most recent baseline file for each node.
After running an installation with this option, the /install/ba
seline directory contains two files, the one created by the
last installation before this one, and the one created by this
installation.
-r Launches installs on remote nodes that have the Server Process
Manager (spm) running. Requires the use of the -c or -C option,
as well as either the -d or the -k option.
-s authorized_area
specifies the pathname of the Authorized Area from which the
tool will install software. This argument is required.
-u Using the baseline file on each target node, updates each
product to the most current version of that product available
in the Authorized Area. Incompatible with -c, -C, -d, -k, or -u
options.
-v Presents detailed informational listings during installation.
-x forces the installation program to continue even if it
encounters an error; often the error can be corrected without
having to rerun the entire installation procedure.
EXAMPLES
The following examples illustrate the use of install++.
install++ -s //color -c //myhome/myfile -p -v -x //myhome
installs software on the target node //myhome from the Authorized Area
at //color, according to the configuration file //myhome/myfile. Because the
program is invoked without the -k or -d options, the configuration
will proceed interactively.
FILES
[authorized_area[/install/tools/install++ (COFF format, for SR10 based systems)
[authorized_area[/install/tools_sr9/install++ (OBJ format, for pre-SR10 based systems)
SEE ALSO
config
See the file [authorized_area]/install/help/config.hlp for a
description of the config tool. The install++ program invokes the
CONFIG program during its configuration phase..