POLYCENTER Software Installation Utility Developer's
Table 3-2 describes additional constraints on the string data type.
Table 3-2 String Data Type Constraints
None; any character may appear in any position.
Access control entry (ACE)
Specifies an ACE for a directory or file.
Specifies an operating system command that you want to execute during a
Specifies the name of a hardware device.
Specifies a file name (without a device or directory specification).
Specifies a rights identifier.
Specifies the name of a module in a library.
Processor model name
Specifies the model identification of a particular computer system.
Relative directory specification
Specifies the directory name and, if necessary, the directory path,
relative to the root directory specification.
Relative file specification
Specifies the directory path and file name, relative to the root
Root directory specification
Specifies the directory name and a trailing period (.). If you specify
a directory name and omit the period, it is inserted. If necessary, you
can add the device name.
3.5 Kit Types and Usage
The POLYCENTER Software Installation utility supports seven kit types
that can be grouped into three broad categories:
- Primary kit --- Used to install or upgrade a product. Primary kits
can require prerequisite products to be installed before or
concurrently. Kit types in this category include:
- Full (layered product or application software)
- Operating system
- Platform (product suite)
- Secondary kit --- Used to modify installed products. Kits types in
this category include:
- Partial (changes the product's version)
- Patch (maintenance update)
- Mandatory update
- Transition kit --- Used to register a product that has been
installed using VMSINSTAL or some method other than the DCL command
PRODUCT INSTALL. The kit type in this category is as follows:
Use the PRODUCT PACKAGE command to package (or build) a product kit.
The output of the packaging process is an installable kit (in either
sequential copy format or reference format) that contains:
- Product material (usually present) --- The files that make up the
product. Usually, the installation of a product kit copies files to the
target disk. However, there are exceptions:
- A transition kit never provides files.
- A platform kit references other products; it may or may not provide
common files for the product suite.
- Since product material is not a requirement for any type of kit,
you may create "skeleton" kits for testing purposes that do
not modify the target disk.
- A product description file (required) that drives the installation
process --- It defines the managed objects that are provided or created
and contains directives for the installation utility. In addition, it
can include options for the installer to select, declare software
references to other prerequisite products, and invoke command
procedures you write to augment the installation process.
- A product text file (optional) that provides text modules for use
during the installation process.
- Temporary files such as command procedures (optional) that are used
during the installation process but are not left on the user's system.
The full product name (that is, the string
producer-base-product) must be unique among all products
installed on a system. This implies, for example, that there could be
two FORTRAN compilers installed from different companies (such as
DEC-AXPVMS-FORTRAN and XYZCORP-AXPVMS-FORTRAN), but there cannot be two
patch kits with the same full name that are intended to apply to
different products (such as ABC-AXPVMS-ECO1 for ABC-AXPVMS-COBOL and
ABC-AXPVMS-ECO1 for ABC-AXPVMS-C).
The following sections describe each type of kit and provide examples
of their product description files.
3.5.1 The Full Kit Type
A full kit provides layered product application software and is the
most common type of kit. The PDF for a full kit must contain a PRODUCT
statement with the keyword full and an END PRODUCT
statement, as shown in the following example:
product CPQ AXPVMS TEST_A V2.0 full ;
end product ;
The full kit has the following characteristics:
- It contains all of the material for the product. Therefore, it can
be used to install the product for the first time or it can upgrade a
previously installed version of the product.
- The product can be removed, configured, or reconfigured.
- Its PDF can contain OPTION and SOFTWARE statements.
Example 3-1 shows a full kit that references another product.
|Example 3-1 PDF for a Full Kit That
References Another Full Kit
product HP AXPVMS FORTRAN V7.1-1 full ; (1)
if (not <software HP AXPVMS VMS version minimum V7.1>) ;(2)
software HP AXPVMS FORRTL version minimum V7.1 ;
end if ;
information STARTUP_TASK phase after ;
information RELEASE_NOTES phase after ;(3)
file [SYSHLP]FORTRAN.RELEASE_NOTES release notes ;(4)
file [SYSHLP]FORTRAN_RELEASE_NOTES.PS ;
file [SYSHLP]FORTRAN_RELEASE_NOTES.DECW$BOOK ;
if (<software DEC AXPVMS FORTRAN90>) ;(5)
error REMFORT90 ;
end if ;
option FORTRAN_90 ;(6)
file [SYSEXE]F90$MAIN.EXE generation 2 ;
file [SYSMSG]F90$MSG.EXE generation 2 ;
module F90CLD.CLD type command generation 2 module F90 ;
module F90HELP.HLP type help generation 2 module F90 ;(7)
end option ;
option FORTRAN_77 ;
file [SYSEXE]FORT$MAIN.EXE generation 1 ;
file [SYSEXE]FORT$FSPLIT.EXE generation 1 ;
file [SYSMSG]FORT$MSG.EXE generation 1 ;
file [SYSMSG]FORT$MSG2.EXE generation 1 ;
module DEC_FORTCLD.CLD type command
generation 1 module FORTRAN ;
module DEC_FORHELP.HLP type help
generation 1 module FORTRAN ;
end option ;
file [SYSLIB]FORSYSDEF.TLB generation 5 ;
file [SYS$STARTUP]FORT$STARTUP.COM generation 1 protection private ;(8)
file [SYSTEST]FORT$IVP.COM generation 1 protection private ;
execute test "@PCSI$DESTINATION:[SYSTEST]FORT$IVP.COM" ;(9)
end product ;
- The PRODUCT statement identifies this as a
complete layered product kit for installation of (or upgrade to)
FORTRAN V7.1-1 on an OpenVMS Alpha system.
- The IF...END IF group conditionally executes
statements within the group based on the evaluation of the IF function.
In this example, the SOFTWARE statement is executed only if the system
is running a version of OpenVMS earlier than V7.1. This SOFTWARE
statement creates a software reference to the product FORRTL. If FORRTL
V7.1 or later is already installed, the software dependency is
satisfied; otherwise, FORRTL is automatically installed concurrently
- This INFORMATION statement causes a message to
be displayed after the product has been installed. Text is obtained
from the module RELEASE_NOTES in the PTF:
=prompt Type HELP FORTRAN Release_notes for release notes location
- This FILE statement copies file
FORTRAN.RELEASE_NOTES to SYS$SYSDEVICE:[VMS$COMMON.][SYSHLP] (the same
as SYS$COMMON:[SYSHLP]) unless the user specifies a different
destination. The RELEASE NOTES keyword phrase tags this file in the kit
so that the PRODUCT EXTRACT RELEASE_NOTES command can be used to
extract this file from the kit.
- This IF statement determines whether or not
the product FORTRAN90 is installed. If it is installed, text from the
module REMFORT90 in the PTF is displayed and the user is asked if he
wants to terminate the operation:
=prompt PRODUCT REMOVE FORTRAN90 before installing HP Fortran
The obsolete DEC Fortran 90 product must be removed before HP Fortran
is installed. To do this, use the command:
PRODUCT REMOVE FORTRAN90
Note that if the ABORT keyword had been used on the ERROR
statement, the operation would terminate unconditionally. ABORT was not
used because the ABORT keyword was introduced in OpenVMS V7.1 and this
kit can be installed on earlier versions of OpenVMS.
- This OPTION...END OPTION group conditionally
provides files and library modules associated with the FORTRAN 90
compiler. The user is asked a question from text module FORTRAN_90 in
=prompt Compaq Fortran 90 compiler
This option selects the Compaq Fortran 90 compiler.
By default, the OPTION statement displays only text from the prompt
line. However, if the user specifies the /HELP qualifier on the PRODUCT
INSTALL command, then both prompt and extended help text is displayed
(two lines in this case).
- The MODULE statement installs the help text
module F90 from the file F90HELP.HLP in the default help library
[SYSHLP]HELPLIB.HLB. The file F90HELP.HLP is not left on the system
because a FILE statement is not used.
- The PROTECTION PRIVATE keyword phrase on this
FILE statement sets the file protection to (S:RWED, O:RWED, G, W),
giving general users no access.
- The EXECUTE TEST statement executes the
functional test for the product (the installation verification
procedure) after the product has been installed. If the test fails, the
user is informed but the product is not removed. The user can use the
PRODUCT REMOVE command to delete the product.