Document revision date: 19 July 1999

1. This prompt allows you to choose options 1 through 4.
2. This prompt is displayed only if you select option 2 or option 3. If you enter the name of a print queue, the system displays a message saying that the release notes have been queued successfully to the printer. If you do not specify a print queue, the release notes are sent to SYS$PRINT by default.
3. This prompt allows you either to continue or to end the installation. The default is to end the installation.
   If the product does not supply release notes, VMSINSTAL.COM displays two error messages. It also asks whether you want to continue or to end the installation, as follows:

   %VMSINSTAL.COM-W-NOFILE, New File facvvu.RELEASE_NOTES does not exist. %VMSINSTAL.COM-W-NORELNOTE, unable to locate release notes. *Do you want to continue the installation [N]:

   
   To continue the installation (whether or not release notes are available), enter Y (for YES) and press Return.

You can use the Alternate Root option to install the product on a system disk other than that of the running system. You might use this option to test a layered product without disturbing the running system.

The operating system in the alternate root must be complete and have the same version or update level as the running system. All files and software products that the product installation refers to must be present in the alternate root.

If you specify option R, the product is installed on the alternate root. However, you cannot create accounts or request a system reboot on an alternate root.

3.7 Using the POLYCENTER Software Installation Utility

The POLYCENTER Software Installation utility is used to 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 asked during the product installation procedure.

Perform POLYCENTER Software Installation utility operations from the DCL prompt. Use the following command format to invoke each operation:

$ PRODUCT subcommand product-name[/qualifier1,...]

For example, to install COBOL Version 2.2 and the latest version of Fortran, enter the following command:

$ PRODUCT INSTALL COBOL/VERSION=2.2,FORTRAN [Return] The following products have been selected: DEC AXPVMS COBOL V2.2 Layered Product DEC AXPVMS FORTRAN V7.0 Layered Product Do you want to continue? [YES] [Return]

Section 3.8 describes installation.

You can enter PRODUCT commands at the DCL prompt ($) or in a DCL command procedure. Refer to the OpenVMS System Management Utilities Reference Manual for subcommand syntax information.

To run the POLYCENTER Software Installation utility as a batch job, see Section 3.8.6.

Table 3-3 lists DCL commands the POLYCENTER Software Installation utility can perform and describes each of them.

Table 3-3 DCL Commands and Descriptions

DCL Command	Description
PRODUCT CONFIGURE	Creates a product configuration file (PCF)
PRODUCT COPY	Copies a software product kit or converts it to another format
PRODUCT EXTRACT FILE	Retrieves a specified file or files from a software product kit packaged in sequential format
PRODUCT EXTRACT PDF	Retrieves the product description file (PDF) from a software product kit packaged in sequential format
PRODUCT EXTRACT PTF	Retrieves the product text file (PTF) from a software product kit packaged in sequential format
PRODUCT EXTRACT RELEASE_NOTES	Retrieves the release notes for a selected product
PRODUCT FIND	Displays the name of product kits found in a specified directory
PRODUCT INSTALL	Installs one or more software products and updates the product database
PRODUCT LIST	Lists a file or files contained in a specified product kit that is packaged in sequential format
PRODUCT PACKAGE	Creates a software product kit.
PRODUCT RECONFIGURE	Modifies the configuration choices for an installed product and updates the product database
PRODUCT REGISTER PRODUCT	Records product information in the product database
PRODUCT REGISTER VOLUME	Records a volume label change of the volume containing the installed products
PRODUCT REMOVE	Removes a product from the system and from the product database
PRODUCT SHOW HISTORY	Displays in chronological order the operations performed on software products
PRODUCT SHOW OBJECT	Displays information about objects created during software product installation
PRODUCT SHOW PRODUCT	Displays information about installed products
PRODUCT SHOW UTILITY	Displays information about the POLYCENTER Software Installation utility

Privileges Required

The POLYCENTER Software Installation utility requires specific privileges to perform certain operations, as shown in Table 3-4.

Table 3-4 Privileges Required by the POLYCENTER Software Installation Utility

Operations	Privileges Required
COPY, EXTRACT, FIND, LIST, PACKAGE	None
CONFIGURE, SHOW	SYSLCK
REGISTER	SYSLCK and SYSPRV (or a system UIC)
INSTALL, RECONFIGURE, REMOVE	SYSLCK, SYSPRV (or a system UIC), TMPMBX, and CMKRNL

Note that commands you execute from the kit you are installing might require additional privileges. Check the installation guides that you receive with product kits for these privileges.

3.7.1 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 requirements (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, producer, 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 automatically by the POLYCENTER Software Installation utility. When products are installed, the files and other objects 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 installed 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.

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 either 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 PDF, the PTF, 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.

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 (for example, DEC)
• 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 to the format tmmnn-ue, described in Section 3.7.3.1.
• kit_type identifies a kit type specified as a value from 1 through 7, as shown in Table 3-5.

Table 3-5 PDF Kit Types and Values

Value	Type of Kit	Description
1	Full	Layered product (application) software.
2	Operating system	Operating system software.
3	Partial	An upgrade to currently installed software that replaces or provides new files. Installation of this kit changes the version of the product.
4	Patch	A correction to currently installed software that replaces or provides new files. Installation of this kit does not change the version of the product.
5	Platform	An integrated set of software products (product suite).
6	Transition	Product information used to register (in the POLYCENTER Software Installation database) a product that was installed by VMSINSTAL or other mechanism. This kit includes only a PDF and (optionally) a PTF; it does not provide product material.
7	Mandatory update	A required correction to currently installed software that replaces or provides new files. Installation of this kit does not change the version of the product. Functionally the same as a patch kit.

3.7.3.1 Version Identification Format

The version of the software product kit is in the format tmmnn-ue. This format is described in Table 3-6.

Table 3-6 Format of tmmnn-ue Version Identification

t	The type of version (a single uppercase alphabetic character).
mm	The major version number (decimal integer 01 through 99).
nn	The minor version number (decimal integer 00 through 99).
-	The hyphen is required in all cases. When both update level (u) and maintenance edit level (e) are omitted, the version will end with a hyphen and the file name will have a double hyphen (- -) preceding the kit type.
u	The update level (decimal integer 1 through 999). The level is optional.
e	The maintenance edit level (one or more alphanumeric characters beginning with an alphabetic character). This level is optional.

The following table of examples shows how to use the format:

Example	Description
V6.1	In this example: Version type: V Major release: 06 Minor release: 01 Update level: 0 (implicit) No edit level
V6.1-1H2	In this example: Version type: V Major release: 06 Minor release: 01 Update level: 1 Edit level: H2
T6.2-FT2	In this example: Version type: T Major release: 06 Minor release: 02 Update level: 0 (implicit) Edit level: FT2

3.7.3.2 Software Product Name Examples

The following examples show how the format is used for one sequential and two reference copy format kits:

• A sequential copy format kit for DEC Softwindows for OpenVMS VAX 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 maintenance 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-T0700-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 V7.0-FT2. The type of version is T, the major version number is 7, and the minor version number is 0. There is no update level because the first character after the hyphen is not a digit. The maintenance edit level is FT2 and the kit_type is 2 (operating system).

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 configuration 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 because this is a new choice, then the default configuration choice comes from the PDF. It can be changed.

Some 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 during an installation, you can answer a question without recording your answer in the PCF. This is useful for responding 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 installer 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 installation procedure.

To create a PCF, use the PRODUCT CONFIGURE command. For example:

$ PRODUCT CONFIGURE CHESSMASTER

The POLYCENTER Software Installation utility creates a PCF in your current default directory. The default PCF is named DEFAULT.PCSI$CONFIGURATION. To override the default file name or directory, use the /CONFIGURATION=OUTPUT qualifier. Refer to the sample procedure in the next section.

3.7.4.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
Return	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 installations or upgrades. If the Defer option is not in effect, this entry cannot 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, including the Defer option, is not written into the PCF and is not used when the PCF is used for future installations or upgrades. In this case, the default for the future installation or upgrade will come from the PDF or PDB.
F17	Toggles the Defer option. By default, the Defer option is not in effect.
F18	Toggles the Write option. By default, the Write option is in effect.

Press the Return key after each response.

Example 3-1 shows how to use keys F17 and F18 in the PCF. Note that this is an example only and does not necessarily represent an actual PCF for a product. A description of the callouts follows the example.

Example 3-1 Sample Procedure for Creating a PCF

$ PRODUCT CONFIGURE VMS/SOURCE=SYS$SYSDEVICE:[VMS$COMMON]/LOG - _$ /CONFIGURATION=(OUTPUT=MYPCF)[Return] The following product has been selected: DEC AXPVMS VMS V7.2 [Available] Do you want to continue [YES] [Return] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. *** DEC AXPVMS VMS V7.2: OpenVMS Operating System Copyright © 1998 Compaq Computer Corporation Compaq Computer Corporation Do you want the defaults for all options? [YES] N [Return] (1) Accounting Log Report Generator Utility [YES] [F17] (2) %PCSIUI-I-DEFER, that item has been deferred; please set the default value Accounting Log Report Generator Utility [YES] [F17] (3) %PCSIUI-I-UNDEFER, that item is no longer deferred; please set the value Accounting Log Report Generator Utility [YES] [F17] (3) %PCSIUI-I-DEFER, that item has been deferred; please set the default value. Accounting Log Report Generator Utility [YES] [Return] (4) Access Control List Utilities [YES] [F18] (5) %PCSIUI-I-UNWRITE, that item will not be written to configuration file; please set the value. Access Control List Utilities [YES] [Return] (6) Print and Batch Queue Utilities [YES] NO (7) DECdtm Distributed Transaction Manager [YES] [Return] (8) Do you want the defaults for all suboptions? [YES] NO . . . Programming Support [YES] [Return] Do you want the defaults for all suboptions? [YES] NO . . . Do you want to review the options ?[NO] [Return] (9) %PCSI-I-WRICON, writing configuration file SYS$SYSDEVICE:[VMS$COMMON]MYPCF.PCSI$CONFIGURATION;1 (10) %PCSIUI-I-SUCCONFIG, CONFIGURE operation completed successfully $

The callouts in the example mark the following actions:

	privacy and legal statement
6017PRO_006.HTML