| Previous | Contents | Index |
When you use /REMOTE, the following logical names must be defined:
PCSI$SYSDEVICE:[SYSx.] |
| 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.
$ 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.
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.
PRODUCT COPY product-name /DESTINATION=device-name:[directory-name] [/qualifiers]
The PRODUCT COPY command allows you to compress a sequential kit. 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. You cannot create a kit in compressed format directly from a kit in reference 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.
If you copy a product kit that is signed and has an associated manifest file in the source directory, both the kit and its manifest are copied to the destination directory. A manifest file is used for product kit validation. It must have a file name and file type that match the file specification of the product kit, with _ESW appended to the file type.
product-name
Names the product, or list of products, to copy.
/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 I64 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-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). 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:
- 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. /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, 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 COPY ABC /SOURCE=[SHERMAN.ABC] -
_$ /DESTINATION=[KITS] /FORMAT=SEQUENTIAL
|
The command in this example converts product kit ABC, located in the [SHERMAN.ABC] directory on the user's default device, to a sequential copy in the [KITS] directory on the user's default device.
Deletes one or more patch recovery data sets in order of creation date, starting with the oldest one first. A recovery data set is created when a patch kit is successfully installed with the /SAVE_RECOVERY_DATA qualifier. Recovery data sets are used to uninstall patches when you use the PRODUCT UNDO PATCH command.Note that once patch recovery data is deleted, you cannot uninstall any patch that is associated with this data. Installed patches are not affected when you use the PRODUCT DELETE RECOVERY_DATA command.
PRODUCT DELETE RECOVERY_DATA [/qualifiers]
None.
/ALL (default)
Selects all patch recovery data sets to be deleted. The recovery data is deleted in the order it was created, starting with the oldest set first. If you omit this qualifier from the command line, the effect is the same as if you specified it./BEFORE=time
Selects patch recovery data sets created before the specified date and time. You can specify time as an absolute time, as a combination of absolute and delta times, or as one of the following keywords:
TODAY (default) TOMORROW YESTERDAYFor information about specifying time values. see the OpenVMS User's Manual.
/OPTIONS=keyword
/NOOPTIONS (default)
Specifies PRODUCT command options. The keyword is:
NOCONFIRM Omits the confirmation dialog that asks the user to verify the recovery data sets that have been selected for processing. /LOG
/NOLOG (default)
Displays the file specifications of the files within the recovery data sets that are being deleted./OLDEST=count
Specifies the number of oldest recovery data sets that you want to delete. For example, if you specify /OLDEST=2, the PRODUCT DELETE RECOVERY_DATA command deletes the two oldest recovery data sets. If you do not specify a number with this qualifier, the default value is 1./REMOTE
/NOREMOTE (default)
Selects recovery data sets located on a privately mounted system disk. By default, PCSI searches the currently booted system disk for recovery data sets.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.]
$ PRODUCT DELETE RECOVERY_DATA /OLDEST=2
|
The command in this example deletes the two oldest recovery data sets starting with the one that was created first, followed by next oldest recovery data set. If, for example, three patch recovery data sets are on the system disk, you still have one set preserved after this operation completes.
Remember that once a patch recovery data set is deleted, you cannot uninstall the patch kit associated with the deleted recovery data. The installed patch kits, however, are not affected by this action.
Retrieves a user-specified file or files from a software product kit. The original name of the file is preserved when it is extracted.
PRODUCT EXTRACT FILE product-name[,...] [/qualifiers]
product-name
Names the product, or list of products, from whose kits the selected file or files are to be retrieved. This parameter is required.
/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 I64 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 the location where the utility is to place all the files that the user indicates are to be retrieved. If the device name is not provided, the default is the user's default device. If the directory name is omitted, or the /DESTINATION= qualifier is not specified, the default is the user's default directory. The EXTRACT FILE operation ignores the PCSI$DESTINATION logical name whether or not you use the /DESTINATION qualifier./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). 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 specifications of the files that are extracted from 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:
- 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./SELECT=filename[,...]
Specifies the name of a file, or a list of files, to be extracted from the specified product kit. You can use the asterisk (*) and the percent sign (%) wildcard characters for all or part of the file name. The file name can contain a directory specification that includes an ellipsis (...). If you omit this qualifier, all files will be extracted from the specified kit or kits./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 that the logical name PCSI$SOURCE defines. 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 EXTRACT FILE TEST /SELECT=TEST.EXE /SOURCE=[AL]
|
In this example, PCSI extracts the file TEST.EXE from the kit of the product TEST that is in the [AL] directory on the user's default disk. The extracted file TEST.EXE is placed in the user's current default directory.
| Previous | Next | Contents | Index |