HP OpenVMS Systems Documentation
Content starts here

HP OpenVMS System Management Utilities Reference Manual

Previous Contents Index 


PPPD> SHOW/ALL=BRIEF TTA0:
Line TTA1: is being used for PPP connections

Debug trace:     OFF       Debug mailbox:
Address comp:    OFF       Max configure:        10  Restart timer:        30
ASN port name:   ASN13     Max failure:           5
Echo failure:           0  Max terminate:         2  Receive ACCM:   FFFFFFFF
Echo intervals:         0  MRU:                1500  Transmit ACCM:  FFFFFFFF
Flow control:    XON/XOFF  MTU:                1500                  00000000
Hangup:          DEFAULT   Mode:           ACTIVE                    00000000
Line type:       TRANSIENT Net protocol:   TCP/IP                    60000000
Magic retries:          0  Protocol comp:  OFF                       00000000
Input speed:     DEFAULT   Receive FCS:          16                  00000000
Output speed:    DEFAULT   Transmit FCS:         16

Counter totals for line TTA0:

Bad FCS packets:                   0   Packets received:                  4
Data lost (chars):                 0   Packets transmitted:               6
Dropped chars:                     0   Runt packets:                      0
Framing errors:                    0   Total chars received:            179
Long packets:                      0

The command in this example displays the current PPP characteristics assigned to port TTA1.

Chapter 17
POLYCENTER Software Installation Utility

17.1 Description

The POLYCENTER Software Installation utility creates, installs, and manages software products. You can use it to do the following:
  • Install and reconfigure software products.
  • Remove software products.
  • Display information from the software product database, such as the names of installed products, the names of patches applied, product dependencies, the names of files provided by product, and historical information about past operations.
  • Locate software product kits that can be installed.
  • Create a software product kit in sequential, compressed, or reference format.
  • List the contents of a software product kit or extract files from the kit, such as release notes or files you specify.
  • Perform other operations such as establishing default configuration choices offered by a product, copying a product kit or converting it to a different format, and registering information about a product in the product database.
  • Uninstall the last patch or set of patches applied to a product.

17.2 Usage Summary

The DCL interface to the POLYCENTER Software Installation utility is the PRODUCT command.

Format

PRODUCT [subcommand product-name [/qualifiers]]

Parameters

subcommand

Specifies an operation you want the POLYCENTER Software Installation utility 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.

Description

To use the POLYCENTER Software Installation utility from the DCL prompt, enter the PRODUCT command, a subcommand, and any required parameters and optional qualifiers. For example: 


  $ 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].

17.3 PRODUCT Commands

The following table describes PRODUCT subcommands:

Subcommand Description
CONFIGURE Creates a product configuration file (PCF)
COPY Copies a software product kit or converts it to another 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 sequential 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 the POLYCENTER Software Installation utility
UNDO PATCH Uninstalls one or more patches for which recovery data has been saved

CONFIGURE

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.

Format

PRODUCT CONFIGURE product-name[,...] [/qualifiers]

Parameter

product-name

Names the product, or list of products, for which product configuration files will be generated.

Qualifiers

/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 Industry Standard 64 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 will be supplied. Keywords are:
CURRENT This is the default. It uses values from the product database, which contains the current values recorded from the last time the product was installed or reconfigured.
PRODUCER Uses values specified by the software manufacturer for this version 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. Each of these, however, can be used with the keyword OUTPUT. 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-type 		Designates 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-type 		Specifies 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:

  1. 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.
  2. 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).
  3. 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.

/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, this utility 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, the POLYCENTER Software Installation utility 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.

Example


$ 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 and then saves your changes in EDITOR_REV2.PCF.

COPY

Copies or converts one or more existing product kits that you specify to product kits in the format you request. For example, you can create a kit in reference format from a kit in sequential format, create a compressed kit from a kit in sequential format, or simply copy a kit to a new location without changing its format.

You cannot create a kit in compressed format directly from a kit in reference format. If you do not have a kit in sequential format, you must first use the PRODUCT PACKAGE command to create a sequential kit from the product materials. Then you can use the PRODUCT COPY command to convert it to compressed format.

Use the /FORMAT qualifier to determine the format of the product kits that you create. Use the /KIT_ATTRIBUTES=FORMAT qualifier to select kits of a particular format to be copied or converted.

Format

PRODUCT COPY product-name /DESTINATION=device-name:[directory-name] [/qualifiers]

Parameter

product-name

Names the product, or list of products, to copy.

Qualifiers

/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 Industry Standard 64 product
VAXVMS Denotes an OpenVMS VAX product
VMS Indicates a product that can be installed on more than one OpenVMS platform

/DESTINATION=device-name:[directory-name]

Specifies a location where the utility will create the sequential or compressed kit. For a reference kit, specifies the top-level directory location where the utility will place files.

If you do not provide a device name, the default is the user's default device. If you omit the directory name, the default is the user's default directory.

The PRODUCT COPY operation ignores the PCSI$DESTINATION logical name whether or not you use the /DESTINATION qualifier.

/FORMAT=keyword

Specifies the output format of the product kit. Keywords are:
   
COMPRESSED Compressed format in which a data compression technique is applied to a sequential kit to produce a .PCSI$COMPRESSED file, which is the compressed form of a sequential kit.
REFERENCE Reference format in which product files are placed in a directory tree for direct access. The utility creates a product description file, with a file type of .PCSI$DESCRIPTION, in the top level of the directory tree.
SEQUENTIAL Sequential format in which product files are placed in a container file having a .PCSI file type.
The default is to preserve the format of the product kit. You must use this qualifier if you want to change the format of the product kit.

/KIT_ATTRIBUTES=keyword([,...])

Selects kits by kit type or kit format, or both. Keywords are:
FORMAT=
format-type 		Designates 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-type 		Specifies 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).
TRANSITION Used to register information about a product that is installed but not recorded in the product database (for example, a product installed by VMSINSTAL). This kit does not provide product material.

/LOG

/NOLOG (default)

Displays the file specification of the product kit file that is created and the files packaged in the kit.

/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:

  1. 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.
  2. 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).
  3. 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.

/OWNER_UIC=uic

Specifies the owner user identification code (UIC) for files created during a copy operation. By default, the user executing the operation owns the software product files. For example, if you are logged in to your own account, you can use this qualifier during a copy operation to assign ownership of the product files to SYSTEM rather than to your own account. Specify the UIC in alphanumeric format (in the form [name]) or in octal group-member format (in the form [g,m]). UIC formats are described in the OpenVMS User's Manual.

/PRODUCER=producer-name

Selects software products that the specified manufacturer produces.

/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, the POLYCENTER Software Installation utility 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

Previous Next Contents Index