3.7 Using the POLYCENTER Software Installation Utility
The POLYCENTER Software Installation utility can help you
install, remove, and manage layered software products on
Alpha or VAX systems. It can also save information about
software products such as system requirements, installation
options, and your answers to questions that the product asked
during the installation procedure.
3.7.1 Interfaces to Use
You can perform POLYCENTER Software Installation util-
ity operations from either the DCL interface or from the
DECwindows Motif interface.
.
The DCL interface is used in most of the examples
throughout the description of the POLYCENTER
Software Installation utility.
Use the following command format to invoke each
operation:
$ PRODUCT subcommand parameter[/qualifier1,...]
For example, to install COBOL Version 5.0 and the latest
version of FORTRAN, enter the following command:
$ PRODUCT INSTALL COBOL/VERSION=5.0,FORTRAN
Return
Return
Section 3.8 describes installation.
To run the POLYCENTER Software Installation utility as
a batch job, see Section 3.8.6.
.
The Motif interface, which is only available if you have
a workstation or an X terminal running DECwindows
Motif for OpenVMS, is described in Section 3.11.
Use the following command format to open the
POLYCENTER Software Installation utility's main
window:
$ PRODUCT
You can add the PRODUCT command to the list of appli-
cations in the Session Manager Applications menu. To do
this, select the Options item in the Session Manager menu
bar, and then select the Menus option. Fill in the appli-
cation name, ``PRODUCT'', and the DCL Command, also
``PRODUCT''. Click on the arrow button that appears,
then click on OK or Apply.
3.7.2 Operations to Perform
Table 3-5 lists operations the POLYCENTER Software
Installation utility can perform and how to initiate them from
each interface.
3.7.3 Product Files and Databases
The following files are used by the POLYCENTER Software
Installation utility:
.
The product description file (PDF), is provided by the
software manufacturer. It contains all the information
the POLYCENTER Software Installation utility needs for
installing either a software product or a set of software
products. The PDF includes a list of configuration choices
the product offers, default choices, and product require-
ments (such as minimum hardware configurations and
system parameter values).
.
A product text file (PTF), is optionally supplied by the
software manufacturer. It provides information about the
product. The information includes product name, pro-
ducer, configuration choice descriptions, and message text
used during product installation.
.
A product configuration file (PCF), is optional. It may
be supplied by software manufacturer, or you can create
it by using the CONFIGURE operation. A PCF contains
responses to some or all of the installation questions for a
product. It can provide default or required choices, which
may differ from the default choices provided in the PDF.
.
The product database (PDB), is created automati-
cally by the POLYCENTER Software Installation utility.
When products are installed, the files and other ob-
jects that make up the product, such as directories and
accounts, are recorded in the PDB. The configuration
choices made during installation are also recorded.
You can access the PDB to show what products are in-
stalled and the dependencies between them. You can also
list the files and other objects that make up each product,
or the history of installation and upgrade activity.
3.7.4 Format of Software Product Kits
Software products compliant with the POLYCENTER
Software Installation utility are distributed in one of two
formats:
.
Sequential copy format. In this form, the PDF, the PTF,
and all files that comprise the product are packaged in a
single container file. This container file can be placed ei-
ther on a random-access device, such as a compact disc,
or on a sequential access device, such as a magnetic tape.
Most layered products are distributed in sequential copy
format.
.
Reference copy format. In this form, the product descrip-
tion file and all files that comprise the product are placed
in a directory tree on a random-access device. OpenVMS
is distributed in reference copy format on CD-ROM.
3.7.5 Software Product Name Conventions
A software product kit packaged in sequential copy format
has a container file named in the following format:
producer-base-product-version-kit_type.PCSI
A software product kit packaged in reference copy format
has a product description file in the root directory named in
the following format:
producer-base-product-version-kit_type.PCSI$DESCRIPTION
Each subfield is separated by a hyphen and is defined as
follows:
.
producer is the legal owner of the software product.
.
base is the base system that specifies the hardware
and software platform on which the product runs (for
example, AXPVMS or VAXVMS).
.
product is the name of the software product.
.
version identifies the version according the format
tmmnn-ue , described in Section 3.7.5.1.
.
kit_type identifies a kit type specified as a value from 1
through 7, as shown in Table 3-6.
3.7.5.1 Version Identification Format
The version of the software product kit is in the format
tmmnn-ue . This format is described in Table 3-7.
Reading a Displayed Version
The tmmnn-ue format used in file names is very similar to
the format used to display versions or to enter versions us-
ing the /VERSION qualifier. However, when versions are
displayed, leading zeros are omitted in mm and nn , and if
neither u nor e is present, the hyphen (-) is omitted. When
you read a displayed version, keep the following guidelines in
mind:
.
If a hyphen is present and the first character after the
hyphen is a digit, then the leading digits after the hyphen
are the update level. If nondigit characters are present,
the maintenance edit level consists of the first nondigit
character and all following characters. If nondigit char-
acters are not present, the maintenance edit level is blank.
.
If a hyphen is present and the first character after the
hyphen is a nondigit character, the update level is zero
(0) and the maintenance edit level consists of all of the
characters after the hyphen.
.
If no hyphen is present, the update level is zero and the
maintenance edit level is blank.
3.7.5.2 Looking at Software Product Name Examples
The following examples show how the format is used for a
sequential copy format kit and two reference copy format
kits:
.
A sequential copy format kit for DEC Softwindows for
OpenVMS VAX and that requires a double hyphen has
the following format:
DEC-VAXVMS-SOFTWIN-V0101--1.PCSI
This format shows that the producer is DEC (Digital),
the base is VAXVMS (OpenVMS VAX), the product is
SOFTWIN, and the version is V1.1. The type of version
is V, the major and minor version numbers are each 1.
There are no update or maintenance edit levels. The kit_
type is 1 (full).
.
A product description file in a reference copy format kit
for OpenVMS Alpha has the following format:
DEC-AXPVMS-VMS-V0601-1H2-2.PCSI$DESCRIPTION
This format shows that the producer is DEC (Digital),
the base is AXPVMS (OpenVMS Alpha), the product
is OpenVMS, and the version is V6.1-1H2. The type of
version is V, the major version number is 6, the minor
version number 1, the update level is 1, and the main-
tenance edit level is H2. The kit_type is 2 (operating
system).
.
A product description file in a reference copy format
kit for a field test version of OpenVMS Alpha has the
following format:
DEC-AXPVMS-VMS-T0602-FT2-2.PCSI$DESCRIPTION
This format shows that the producer is DEC (Digital),
the base is AXPVMS (OpenVMS Alpha), the product is
OpenVMS, and the version is V6.2-FT2. The type of ver-
sion is T, the major version number is 6, and the minor
version number is 2. There is no update level because the
first character after the hyphen is not a digit. The main-
tenance edit level is FT2 and the kit_type is 2 (operating
system).
3.7.6 Creating a Product Configuration File (PCF)
You can create a PCF before or during an installation. You
can also create more than one PCF for each product, thereby
helping you to customize software installations for unique
hardware situations or for different usage patterns within a
group.
If a PCF is present and it contains a response for a config-
uration choice, the default for that choice comes from the
PCF. The PCF specifies whether the choice can be changed
or whether it is required.
If a PCF is not present or does not contain a response for a
configuration choice, the default choice comes from one of
two places:
.
If the product database (PDB) contains an entry for the
choice that was made in a previous installation, then the
PDB entry becomes the default configuration choice. It
can be changed.
.
If the PDB does not contain an entry for the choice, either
because the product was not previously installed or be-
cause this is a new choice, then the default configuration
choice comes from the PDF. It can be changed.
3.7.6.1 Configuration Options
Some of the options available for customizing the PCF are:
.
Saving your answer. You can specify that your response
to a question (rather than the current default value) be
stored in the PCF.
.
Not saving your answer. When creating a PCF dur-
ing an installation, you can answer a question without
recording your answer in the PCF. This is useful for re-
sponding to questions that are specific to a single system
or installation.
.
Deferring a question so that it is asked again during a
future installation. For example, you might want an in-
staller to verify that a particular response is still valid for
the systems on which each installation is being performed.
.
Preventing a question from being asked again. If you do
not defer a question when you create a PCF, the response
recorded in the PCF is used during future installations.
The installer is not prompted for the information. This
reduces the length and complexity of the actual installa-
tion procedure.
3.7.6.2 Configuration Commands
You can use either DCL or the DECwindows Motif inter-
face to define a PCF. Whichever you use, the POLYCENTER
Software Installation utility creates a PCF in your current
default directory. The default PCF is named DEFAULT.PCSI$CONFIGURATION.
If you want to override the default file name or directory,
use the /CONFIGURATION=OUTPUT qualifier. See the
OpenVMS System Management Utilities Reference Manual .
To define a PCF from DCL, invoke the PRODUCT
CONFIGURE command. For example:
$ PRODUCT CONFIGURE CHESSMASTER
To create a PCF using the DECwindows Motif interface,
choose either Installation or Reconfiguration from the Mode
menu. Select the Source/Work qualifier and enter a valid
source location for the Product Definition File (PDF). Select
one or more products. Select Write Configuration from
the Qualifiers menu. (You may also wish to select Read
Configuration.) Enter a file name for Read Configuration,
Write Configuration, or both. Expand the selected product or
products to see the Write/NoWrite and Defer/NoDefer icons.
Make configuration choices by selecting or canceling op-
tions and setting the Write and Defer options. The Write icon
is a pen. If the pen is down, Write is set; if the pen us up,
NoWrite is set. The Defer icon is an arrowhead. If the ar-
rowhead is highlighted, Defer is in effect; if the arrowhead is
not highlighted, NoDefer is in effect.
When the configuration choices are correct, click on the
Apply button for Write Configuration to write the PCF. If
you do not want to perform the actual installation or recon-
figuration, click on the Reset button instead of the Install or
Reconfigure button.
3.7.6.3 Recording Configuration Choices
After defining the PCF, the POLYCENTER Software
Installation utility prompts you with questions about the
product. Determine how and whether your responses are
recorded in the PCF by responding to the questions and using
two predefined function keys. The following table shows how
your responses configure the PCF:
Key
Action by the POLYCENTER Software Installation
utility
Accepts the default or explicitly entered choice for
the current operation and for entry into the PCF, and
then moves to the next choice.
If the Defer option is in effect, this entry can be
changed when the PCF is used for future installa-
tions or upgrades.
If the Defer option is not in effect, this entry can-
not be changed when the PCF is used for future
installations or upgrades.
If the Write option is in effect, this entry, including
the Defer option, is written into the PCF and used
when the PCF is used for future installations or
upgrades.
If the Write option is not in effect, this entry, includ-
ing the Defer option, is not written into the PCF and
is not used when the PCF is used for future instal-
lations or upgrades. In this case, the default for the
future installation or upgrade will come from the
PDF or PDB.
Toggles the Defer option. By default, the Defer option
is not in effect.
Toggles the Write option. By default, the Write option
is in effect.
Press the Return key after each response.
The callouts in Example 3-1 mark the following actions:
To review your configuration responses, specify the name of
the PCF on the PRODUCT CONFIGURE command line
and then scan your answers. Press the Return key to leave
your answers unchanged.
When you use a single DCL command or Motif operation
to install or configure more than one product and write the
responses to a PCF, the information for all of the products
installed or configured is contained in a single PCF. Use sep-
arate operations to install or configure a set of products when
you want to keep each product's configuration values in its
own PCF.
3.7.6.4 Modifying an Existing PCF
You can modify an existing file by using DCL or Motif. In
DCL, specify the name of the PCF to be modified and the
name of the PCF to be created. Include both the INPUT and
the OUTPUT keywords with the /CONFIGURATION qual-
ifier on the PRODUCT CONFIGURE command line. For
example, read the default values in the file PRODUCTA_
REV1.DAT, make changes to the file, and save the changes to
PRODUCTA_REV2.DAT, the output file:
$ PRODUCT CONFIGURE -
_$ /CONFIGURATION=(INPUT=PRODUCTA_REV1.DAT,OUTPUT=PRODUCTA_REV2.DAT) -
_$ PRODUCTA
In DECwindows Motif, select both Read Configuration and
Write Configuration as described in Section 3.7.6.2.
3.7.7 Using a Product Database
The POLYCENTER Software Installation utility automati-
cally stores information about product installation, configu-
ration choices, and object, such as files and directories, that
make up the product in the product database. The product
database is useful for recalling information about products in-
stalled on your system and for detecting and tracking product
dependencies.
3.7.7.1 Adding Information to the Database
Although the POLYCENTER Software Installation utility
stores product information for you automatically, you can also
add your own information. When you perform a task, you
can include a remark-a comment to be recorded in the prod-
uct database-along with the other information about the task
being performed. To add a remark to the product database,
use the /REMARK qualifier with either the PRODUCT
CONFIGURE or PRODUCT REGISTER PRODUCT com-
mand. See the OpenVMS System Management Utilities
Reference Manual for information about these commands
and the /REMARK qualifier.
3.7.7.2 Registering a Noncompliant Product
To register a product that was installed with a tool other than
the POLYCENTER Software Installation utility, enter the
PRODUCT REGISTER PRODUCT command. This com-
mand records information provided by a PDF. For example:
$ PRODUCT REGISTER PRODUCT TOOLCHEST
If you do not have a PDF for a product you want to register,
enter the following command:
$ @SYS$UPDATE:PCSI$REGISTER_PRODUCT.COM
This procedure prompts you for the product name, ver-
sion, and producer. For example, the ``producer'' for Digital
products is ``DEC''. The procedure uses this information
to create a temporary, minimal PDF. It then executes the
PRODUCT REGISTER PRODUCT command to register the
product, and deletes the temporary PDF.
Because PCSI$REGISTER_PRODUCT.COM creates only
a minimal PDF, it cannot register with the POLYCENTER
Software Installation utility database all the information
about the product. For this reason, if a PDF for the product
is available, use it.
Although a ``transition'' PDF is intended specifically for the
PRODUCT REGISTER PRODUCT command, ``full'' and
``operating system'' PDFs can also be registered.
3.7.7.3 Detecting and Tracking Software Dependencies
Some software products depend on other software products
to work correctly. For example, a product might work only
when a specific version of another product is installed on the
system. The POLYCENTER Software Installation utility de-
tects and tracks the dependencies of the products that you
install. The POLYCENTER Software Installation utility also
attempts to satisfy the requirements of multiple products.
In some instances, the POLYCENTER Software Installation
utility is unable to resolve product dependency issues. In such
instances, the POLYCENTER Software Installation utility
provides feedback on the nature of the conflict and asks you
to decide how to proceed.