Software Distributor Administrator Guide (September 2010)

The swverify behavior can be controlled by the enforce_selections option. If
set to false (default), swverify proceeds even when only one software selection is
available in the source. If set to true, swverify proceeds only if all of the software
selections are available.
Phase II: Analysis
The analysis phase for swverify takes place on the host. The host’s environment is not
modified.
The sequential analysis tasks on each host are:
1. Initiate analysis
2. Process software selections. The system accesses the Installed Products Database
(IPD) or depot catalog to get the product information for the selected software:
For installed software, the system checks that all products are compatible with its
uname attributes. This check is controlled by the default option
allow_incompatible:
• If allow_incompatible is set to false, the system produces an error stating
that the product is not compatible with the host.
• If allow_incompatible is set to true, a warning is issued stating that the
product is not compatible.
3. Check for correct states in the filesets (installed, configured or available). For
installed software, swverify also checks for multiple versions that are controlled
by the allow_multiple_versions option:
• If allow_multiple_versions is false, an error is produced that multiple
versions of the product exist and the option is disabled.
• If allow_multiple_versions is true, a warning is issued saying that
multiple versions exist.
4. Check dependencies. An error or warning is issued if a dependency cannot be
met. Dependencies are controlled by the enforce_dependencies option:
• If enforce_dependencies is true, an error is generated telling you the type
of dependency and what state the product is in.
• If enforce_dependencies is false, a warning is issued with the same
information.
• If the dependency is a corequisite, it must be present before the software will
operate.
• If the dependency is a prerequisite, it must be present before the software can
be installed or configured.
5. Execute verify or fix scripts on installed software in prerequisite order.
A verify script is used to ensure that the configuration of the software is correct.
Possible vendor-specific tasks for a verify script include:
78 Installing Software