PRODUCT, PACKAGE
*Conan The Librarian (sorry for the slow response - running on an old VAX)
|
VMS Help PRODUCT, PACKAGE *Conan The Librarian (sorry for the slow response - running on an old VAX) |
|
Creates a software product kit. This operation uses a product
description file (PDF) and an optional product text file (PTF) to
produce a kit that contains the images and other files that make
up the product.
During a package operation, the POLYCENTER Software Installation
utility reformats the input PDF file to produce a new output
PDF file. Comments are removed from the output PDF file and
information, such as the size of each file, is added. The input
PTF file is transformed into an output PTF in text library
format.
The PRODUCT PACKAGE command requires the /SOURCE, /DESTINATION,
and /MATERIAL qualifiers.
Format
PRODUCT PACKAGE product-name[,...] [/qualifiers]
/SOURCE=file-specification
/DESTINATION=device-name:[directory-name]
/MATERIAL=(path-name[,...])
| 1 - Parameter |
product-name
Names the product or list of products to be packaged.
| 2 - Qualifiers |
2.1 - /BASE_SYSTEM
/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. The base system name AXPVMS
denotes an OpenVMS Alpha product, VAXVMS denotes an OpenVMS VAX
product, and VMS denotes a product applicable to either OpenVMS
Alpha or VAX.
2.2 - /COPY
/COPY(default)
/NOCOPY
Specifies whether you want the product material files and
associated directories included in the product kit. The /NOCOPY
qualifier can save file processing time when you are debugging a
PDF file and do not need to produce a complete product kit.
The use of /NOCOPY with /FORMAT=SEQUENTIAL is not supported and
produces undefined results.
2.3 - /DESTINATION
/DESTINATION=device-name:[directory-name]
If /FORMAT=SEQUENTIAL is specified, /DESTINATION specifies
the directory where the utility creates the sequential kit. A
sequential kit is a container file that includes the PDF, PTF,
and all the images and other material that make up the product.
The file type of the sequential kit file is .PCSI.
If /FORMAT=REFERENCE is specifed (or defaulted), /DESTINATION
specifies the directory where the utility creates the output
PDF file and optional PTF file. The file types of the PDF and
PTF files are .PCSI$DESCRIPTION and .PCSI$TLB, respectively. The
images and other materials that make up the product are placed in
a directory tree under this directory.
If the device name is not provided, it defaults to the user's
default device. If the directory name is omitted, it defaults to
the user's default directory.
The PRODUCT PACKAGE operation ignores the PCSI$DESTINATION
logical name whether or not you use the /DESTINATION qualifier.
2.4 - /FORMAT
/FORMAT=keyword
Specifies the output format of the product kit. Keywords are:
REFERENCE Reference format in which product files are placed
in a directory tree.
SEQUENTIAL Sequential format in which product files are
placed in <full-product-name>.PCSI, a container
file.
The default is /FORMAT=REFERENCE.
2.5 - /LOG
/LOG
/NOLOG (default)
Displays messages as the POLYCENTER Software Installation utility
performs the operation.
2.6 - /MATERIAL
/MATERIAL=(path-name[,...])
Specifies one or more locations in which the utility can search
for product material files to include in the software product
kit. Material files represent the output of the producer's
software engineering process, that is, all files that make up
the software product, including any command procedures that might
be used during installation.
Note that the location of the PDF and PTF are not specified
with the /MATERIAL qualifier. See the /SOURCE qualifier for more
information.
This is a required qualifier for the PRODUCT PACKAGE command.
Parentheses (()) are optional only when you specify a single
path name. They are required when you specify multiple path
names.
The format for path-name is: device-name:[directory-name]
You can specify path-name as:
A specific directory Only one directory is searched.
A root directory A period (.) following the directory name
denotes a root directory specification.
For example, TEST$:[ABC.FT2.] limits
the search path to subdirectories of
[ABC.FT2].
A wildcard directory The directory name includes one or more
of the wildcard characters asterisk (*),
percent sign (%), or ellipsis (...).
All directories that satisfy the wildcard
specification are searched.
Note that when you use either a wildcard directory or a list of
path names, if files in different directories have the same name,
only the first file found in the search path is used.
When either a specific directory or a wildcard directory is
used, the relative file specification on the file statement in
the PDF file is not used to locate the file. However, when a
root directory is used, the utility appends the relative file
specification from the file statement in the PDF to the root
directory in the material search path to locate files.
In general, use of a specific directory or a root directory is
more efficient than using a wildcard directory. When packaging
a product that contains hundreds of files, you might notice
a significant difference in processing time, depending on the
method you use to specify the path name. The choice of material
path name does no affect the time required to install the kit.
2.7 - /OWNER_UIC
/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.
2.8 - /PRODUCER
/PRODUCER=producer-name
Selects software products that the specified manufacturer
produces.
2.9 - /SOURCE
/SOURCE=file-specification
Specifies the location of the input PDF file. If the device name
is omitted, it defaults to the user's default device. If the
directory name is omitted, it defaults to the user's default
directory. If the file name and file type components of the file
specification are not provided, they default to <full-product-
name>.PCSI$DESCRIPTION.
The optional PTF file, if used, must be in the same directory and
have the same file name as the PDF with a .PCSI$TEXT file type.
If a file named <full-product-name>.PCSI$TEXT is not found, the
package operation does not use a PTF file.
This is a required qualifier for the PRODUCT PACKAGE command. The
logical name PCSI$SOURCE is not used.
2.10 - /VERSION
/VERSION=version-number
Selects software products that have the specified version.
| 3 - Example |
$ PRODUCT PACKAGE VIEWER -
_$ /PRODUCER=ABC /FORMAT=SEQUENTIAL/ LOG -
_$ /SOURCE=[JAMES.TEST.PDF] -
_$ /DESTINATION=DKA200:[PCSI_KITS] -
_$ /MATERIAL=BUILD$:[VIEWER0201.RESULT...]
The directory [JAMES.TEST.PDF] contains the PDF named ABC-
AXPVMS-VIEWER-0201-1.PCSI$DESCRIPTION. This file and the
product material files from the BUILD$:[VIEWER0201.RESULT...]
directory tree are used to create the kit for product VIEWER.
When the PACKAGE operation completes, a sequential kit named
ABC-AXPVMS-VIEWER-0201-1.PCSI is created and placed in the
DKA200:[PCSI_KITS] directory.
|
|
