|
HP OpenVMS Systems Documentation |
|
HP OpenVMS System Management Utilities Reference Manual
The command in this example displays the current PPP characteristics assigned to port TTA1.
Chapter 19
|
$ PRODUCT INSTALL FORTRAN /VERSION=V7.2-3 /SOURCE=DISK1:[KITS] |
This command installs FORTRAN V7.2-3 on your system from a product kit located in DISK1:[KITS].
subcommand
Specifies an operation you want PCSI to perform. If you do not supply a subcommand, the utility prompts you to select one from a list.product-name
Specifies the name of the product to which you want to apply the activity. Some subcommands do not require this parameter. You can use the asterisk (*) and the percent sign (%) wildcard characters for all or part of the product-name. You can specify a list of products separated by commas (,).The product name is the same as the third component of the file name of the product kit. For example, the product name parameter that you would use to refer to a kit named DEC-AXPVMS-FORTRAN-V0702-3-1.PCSI is FORTRAN. A product name can include an underscore character (_) but never a hyphen (-). For example, VMS73_DRIVER is the name of a remedial kit for OpenVMS whose file name is DEC-AXPVMS-VMS73_DRIVER-V0300--4.PCSI.
The following table describes PRODUCT subcommands:
| Subcommand | Description |
|---|---|
| ANALYZE PDB | Verifies the product database and makes minor repairs, if possible. |
| CONFIGURE | Creates a product configuration file (PCF). |
| COPY | Copies a software product kit or converts it to another format such as compressed format. |
| DELETE RECOVERY_DATA | Deletes one or more patch recovery data sets. |
| EXTRACT FILE | Retrieves a specified file or files from a software product kit. |
| EXTRACT PDF | Retrieves the product description file (PDF) from a software product kit. |
| EXTRACT PTF | Retrieves the product text file (PTF) from a software product kit. |
| EXTRACT RELEASE_NOTES | Retrieves the release notes from a software product kit. |
| FIND | Displays the name of product kits found in a specified directory. |
| INSTALL | Installs one or more software products and updates the product database. |
| LIST | Lists the files contained in a software product kit |
| PACKAGE | Creates a software product kit in either sequenti.al or reference format. |
| RECONFIGURE | Modifies the configuration of an installed product and updates the product database. |
| REGISTER PRODUCT | Records information in the product database about one or more installed products that are not yet registered in the database. |
| REGISTER VOLUME | Records a change in volume label in the product database. |
| REMOVE | Uninstalls one or more software products and updates the product database. |
| SHOW HISTORY | Displays in chronological order the operations performed on software products. |
| SHOW OBJECT | Displays information about objects created during software product installation. |
| SHOW PRODUCT | Displays information about installed products. |
| SHOW RECOVERY_DATA | Displays patch recovery data sets in chronological order. |
| SHOW UTILITY | Displays version information about PCSI. |
| UNDO PATCH | Uninstalls one or more patches for which recovery data has been saved. |
Verifies the structural integrity of the product database and, in some circumstances, performs minor repairs on the files in the database.
PRODUCT ANALYZE PDB [/qualifiers]
The product database refers to an interrelated set of files named *.PCSI$DATABASE. These files ordinarily reside in SYS$SYSTEM.When you use this command, PCSI does the following:
- Reads *.PCSI$DATABASE files referenced by the root database file PCSI$ROOT.PCSI$DATABASE and checks all fields for correct syntax.
- Automatically performs minor repairs when a known corruption pattern can be identified and if a repair is feasible.
- Provides instructions for rebuilding the database if an unrecoverable corruption is found.
The PRODUCT ANALYZE PDB command always reads the PCSI$ROOT.PCSI$DATABASE file, even if you also select a subset of the database files for analysis.
None.
/LOCATION=device-name:[directory-name]
Specifies the location of the product database files to be analyzed. Include only a device and directory name. This qualifier is useful if you copy the product database to a temporary directory to perform verification and repair on the copy rather than on the original files.If you do not use this qualifier, the default location of the product database files is SYS$SYSDEVICE:[VMS$COMMON.SYSEXE]. If you omit the device name, PCSI uses your current default device. If you omit the directory name, PCSI uses your current default directory.
/PDB_TYPE=keyword
Specifies that a subset of the product database files is to be analyzed. By default, all database files referenced by the root database file PCSI$ROOT.PCSI$DATABASE are analyzed.Keywords are as follows:
FILE_SYSTEM Selects the PCSI$FILE_SYSTEM.PCSI$DATABASE file for analysis. PROCESSOR Selects the PCSI$PROCESSOR.PCSI$DATABASE file for analysis. PRODUCT=(product-name[,...]) Selects the product specific database files for the named products for analysis. Wildcard characters are permitted in the product name. ROOT Selects the PCSI$ROOT.PCSI$DATABASE file for analysis. /REMOTE
/NOREMOTE (default)
Selects the product database located on a privately mounted system disk. By default, PCSI searches the currently booted system disk for the product database.When you use /REMOTE, the following logical names must be defined:
- PCSI$SYSDEVICE must specify the physical disk name of the target system disk. This disk must be mounted and allocated to the process executing the PRODUCT command.
- PCSI$SPECIFIC must point to a system root on PCSI$SYSDEVICE. It must be defined in the following form, where x is a valid system root:
PCSI$SYSDEVICE:[SYSx.]
| #1 |
|---|
$ PRODUCT ANALYZE PDB
Analyzing product database files in DISK$V83SYS:[VMS$COMMON.][SYSEXE]
...scanned PCSI$ROOT.PCSI$DATABASE;1
...scanned PCSI$FILE_SYSTEM.PCSI$DATABASE;1
...scanned PCSI$PROCESSOR.PCSI$DATABASE;1
...scanned DEC-AXPVMS-DECNET_OSI-V0703-2.PCSI$DATABASE;1
...
...scanned DEC-AXPVMS-VMS-V0803-2.PCSI$DATABASE;1
Completed product database analysis with no errors detected
|
The command in this example verifies the active product database files in their usual location on the system disk in SYS$SYSTEM.
| #2 |
|---|
$ PRODUCT ANALYZE PDB /LOCATION=DKA300:[TEST] /PDB_TYPE=PRODUCT=TCPIP*)
Analyzing product database files in DKA300:[TEST]
...scanned DEC-AXPVMS-TCPIP-V0504-15.PCSI$DATABASE;1
...scanned DEC-AXPVMS-TCPIP_ECO-V0504-155.PCSI$DATABASE;1
...scanned DEC-AXPVMS-TCPIP_ECO-V0504-154.PCSI$DATABASE;1
...scanned DEC-AXPVMS-TCPIP_ECO-V0504-152.PCSI$DATABASE;1
Completed product database analysis with no errors detected
|
The command in this example analyzes the database files in the DKA300:[TEST] directory for the TCP/IP product and all the patch kits that have been applied to it. The root database file PCSI$ROOT.PCSI$DATABASE must also be in this directory.
Creates a product configuration file (PCF) for one or more products. Optionally uses the values in an existing PCF file to create the new PCF.
PRODUCT CONFIGURE product-name[,...] [/qualifiers]
product-name
Names the product, or list of products, for which product configuration files will be generated.
/BASE_SYSTEM=base-system-name
Selects software products whose base system matches the one specified. The base system name identifies both a hardware platform and an operating system. Standard names are:
Name Description AXPVMS Denotes an OpenVMS Alpha product. I64VMS Denotes an OpenVMS Integrity servers product. VAXVMS Denotes an OpenVMS VAX product. VMS Indicates a product that can be installed on more than one OpenVMS platform. /CONFIGURATION=(keyword[,...])
Specifies how the configuration choices are used. Keywords are:
CURRENT Uses values from the product database. These values are the configuration choices made when the product was installed or reconfigured. PRODUCER Uses values specified by the software manufacturer of the product. INPUT=pcf-name Uses values from the specified product configuration file. OUTPUT=pcf-name Writes configuration choices to the specified product configuration file. If no file name is supplied, creates a file named DEFAULT.PCSI$CONFIGURATION in the current default directory. The keywords CURRENT, PRODUCER, and INPUT are mutually exclusive. (CURRENT is the default if none of these keywords is specified.)
The OUTPUT keyword can be used with the CURRENT, PRODUCER, or INPUT keyword.
If you specify only one keyword, you can omit the parentheses.
/HELP
/NOHELP (default)
Controls whether detailed explanations of product options and informational text are displayed. The first time you install a product, these explanations can help you decide which options to select. When you perform subsequent installations or upgrades, you might choose the brief explanations to save time.When /NOHELP is selected, you can request a detailed explanation about a question by performing one of the following actions at the prompt:
- Press the Help key or PF2 key
- Type ? and press the Return key
/KIT_ATTRIBUTES=keyword([,...])
Selects kits by kit type or kit format, or both. Keywords are:
FORMAT=
format-typeDesignates the format of the product kit as follows:
COMPRESSED Compressed format in which a data compression technique has been applied to a sequential kit. A compressed kit has a .PCSI$COMPRESSED file type. REFERENCE Reference format in which product files exist in a directory tree. A .PCSI$DESCRIPTION file in the top level of the directory tree denotes a reference kit. SEQUENTIAL Sequential format in which product files are placed in a container file. A file type of .PCSI indicates a sequential kit. TYPE=
kit-typeSpecifies the type of product kit as follows:
FULL Layered product (application) software. OPERATING_SYSTEM Operating system software. MANDATORY_UPDATE A required correction to currently installed software. Functionally, this type of kit is the same as a patch kit. PARTIAL An upgrade to currently installed software. Installation of this kit changes the version of the product. PATCH A correction to currently installed software. Installation of this kit does not change the version of the product. PLATFORM An integrated set of software products (also called a product suite). /LOG
/NOLOG (default)
Displays the file specification of the configuration file that is created./OPTIONS=keyword
/NOOPTIONS (default)
Specifies PRODUCT command options. The keywords are:
NOCONFIRM Omits the confirmation dialog that asks the user to verify the products that have been selected for the operation. The NOCONFIRM and NODEFAULT_KIT keywords are mutually exclusive.
NODEFAULT_KIT Directs the utility to query the user instead of choosing a default kit when more than one kit that matches the selection criteria for the product is found in the source directory path. The selection criteria include the producer, base system, product name, and product version strings that are embedded in the file name of a kit. If multiple kits are found for a selected product, and NODEFAULT_KIT is not specified, the utility determines the default kit to use by applying the following rules:
- The last character of the kit's file name (1-7) is used to order the kits by kit type. In descending order, the precedence is as follows: full, operating system, partial, patch, platform, transition, and mandatory update.
- The file type is used to order the kits by format. In descending order, the precedence is as follows: compressed (.PCSI$COMPRESSED), sequential (.PCSI), and reference (.PCSI$DESCRIPTION).
- If multiple kits are found with the same file name and file type, but differ in their directory path names, the case of their file specifications, or their file versions, then the first file found by RMS search rules takes precedence.
The NODEFAULT_KIT and NOCONFIRM keywords are mutually exclusive.
NOVALIDATE_KIT Disables validation of software product kits that are signed and have a manifest file in the source directory. /PRODUCER=producer-name
Selects software products that the specified manufacturer produces./REMOTE
/NOREMOTE (default)
Selects the product database located on a privately mounted system disk. By default, PCSI searches the currently booted system disk for the product database.When you use /REMOTE, the following logical names must be defined:
- PCSI$SYSDEVICE must specify the physical disk name of the target system disk. This disk must be mounted and allocated to the process executing the PRODUCT command.
- PCSI$SPECIFIC must point to a system root on PCSI$SYSDEVICE. It must be defined in the following form, where x is a valid system root:
PCSI$SYSDEVICE:[SYSx.]/SOURCE=device-name:[directory-name]
Specifies the disk and directory where the utility searches for the software product kit or kits. If /SOURCE is not specified, the utility searches in the location defined by the logical name PCSI$SOURCE. If PCSI$SOURCE is not defined, and the /SOURCE qualifier is not specified, PCSI searches the current default directory./SPAN_VERSIONS=keyword([,...])
Selects software products whose versions match the specified version criteria. The keywords are:
ABOVE=version Selects versions greater than the version specified BELOW=version Selects versions less than the version specified MINIMUM=version Selects versions greater than or equal to the version specified MAXIMUM=version Selects versions less than or equal to the version specified The ABOVE, BELOW, MINIMUM, and MAXIMUM keywords can be used alone or in combination. For example, /SPAN_VERSIONS= (MINIMUM=V2.1,BELOW=V3.0) selects versions greater than or equal to V2.1 and less than (but not including) V3.0. Using the MAXIMUM keyword instead of BELOW would select versions that include V3.0.
/VERSION=version-number
Selects software products that have the specified version.
$ PRODUCT CONFIGURE EDITOR -
_$ /CONFIGURATION=(INPUT=EDITOR_REV1.PCF,OUTPUT=EDITOR_REV2.PCF)
|
The command in this example reads an existing PCF file named EDITOR_REV1.PCF for a product named EDITOR to obtain default values for its configuration options. Then a configuration dialog allows the user to change and review all options. Finally, the modified configuration values are saved in EDITOR_REV2.PCF.
| Previous | Next | Contents | Index |