Technical data

Installing, Upgrading, and Updating Software
3.7 Using the POLYCENTER Software Installation Utility
The callouts in the example mark the following actions:
! Chooses to select values for individual options instead of accepting default
values for all of the options.
" Requests (by using the defer key, F17) that the installer be given the choice of
whether or not to install the optional example files.
# Toggles the defer option (twice to illustrate the toggle effect).
$ Records the default response [Yes] in the PCF. Because the defer option was
in effect, when the PCF is used during a future installation, the installer can
select the Accounting Log Report Generator utility by default, or can choose
not to select it.
% Requests the nowrite option key (F18) so that this choice will not be written
to the PCF.
& Chooses not to install the Access Control List utilities. Because the nowrite
option is in effect, this choice is not written to the PCF.
’ Chooses not to install the Print and Batch Queue utilities. Because the
nowrite option is not in effect (by default) and the defer option is in effect (by
default), this choice is written to the PCF and the question is not asked again
when the PCF is used during a future installation.
( Accepts the default to install the DECdtm Distributed Transaction Manager.
Because the nowrite option is not in effect (by default) and the defer option is
in effect (by default), this choice is written to the PCF, and the question is not
asked again.
) Requests that the configuration options be displayed.
+> Displays the name of the PCF that has been created,
MYPCF.PCSI$CONFIGURATION. The POLYCENTER Software Installation
utility displays this message only when you enable message logging by using
/LOG with PRODUCT CONFIGURE.
When you use a single DCL command to install or configure more than one
product and write the responses to a PCF, the information for all the products
that are installed or configured is in a single PCF. Use separate 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.4.4 Modifying an Existing PCF
You can use DCL to modify an existing file. 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 qualifier 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
3–22 Installing, Upgrading, and Updating Software