HP OpenVMS Systems Documentation
POLYCENTER Software Installation Utility Developer's Guide
1.3.5 Step 5: Package the Software Components
Package the software components to create a .PCSI file. This step is
fully described in Chapter 5. Use the PRODUCT PACKAGE command and
its qualifiers. The PRODUCT PACKAGE command determines if the PDF and
PTF are syntactically correct and verifies that all listed product
material files can be found.
When a kit has been successfully produced, use the PRODUCT INSTALL, PRODUCT SHOW, and PRODUCT REMOVE commands to verify the installation and removal of the product. Check for correct file placement and protection, test user input, review message text, modify configuration options, verify that execution environment requirements are satisfied, and so forth.
Test your installable kit to make sure that it properly handles any software version dependencies.
The format and content of the database files are controlled by the POLYCENTER Software Installation utility. If an OpenVMS system manager uses the POLYCENTER Software Installation utility to install your product, the utility will expect the database files to exist from that point on.
Caution your product's users not to delete these files or the POLYCENTER Software Installation utility will not be able to detect and manage your product. The complete set of database files must be intact for the utility to access the information in the database.
As a software provider, you can use PDL statements to query the product database to dynamically determine the version of an installed product. The following example illustrates how installation choices are made based on the installed version of OpenVMS on an Alpha system:
if (<software DEC AXPVMS VMS version minimum V6.2> AND <software DEC AXPVMS VMS version below A6.3>) ; file [SYSEXE]TNT$SERVER.EXE generation 5 source TNT$SERVER_V62.EXE ; file [SYSEXE]TNT$UTILITY.EXE generation 1 source TNT$UTILITY_V62.EXE ; file [SYSTEST.TNT]TNT$SERVER_IVP.EXE generation 5 source TNT$SERVER_IVP_V62.EXE ; end if; if (<software DEC AXPVMS VMS version minimum V7.0> AND <software DEC AXPVMS VMS version below A7.1>) ; file [SYSEXE]TNT$SERVER.EXE generation 5 source TNT$SERVER_V70.EXE ; file [SYSEXE]TNT$UTILITY.EXE generation 1 source TNT$UTILITY_V70.EXE ; file [SYSTEST.TNT]TNT$SERVER_IVP.EXE generation 5 source TNT$SERVER_IVP_V70.EXE ; end if;
OpenVMS users can use the DCL command PRODUCT SHOW either to query the product database to show what products are installed and the dependencies between them, to list the files and other objects that make up each product, or to show the history of installation and upgrade activity.
If your installation procedure or the OpenVMS user removes a product,
information about the files and objects associated with the product are
removed from the database. However, the history of the product's
activity from installation to removal is retained in the database.
2.2 Software Product Kit Formats
Figure 2-1 shows how the package operation uses the PDF, PTF, and product material to create a product kit in reference or sequential format. Subsequently, the copy operation can be used to transform a sequential kit into a kit in compressed format.
Figure 2-1 Package Operation
The POLYCENTER Software Installation utility adheres to the following file-naming conventions when
either creating a software product kit or processing PDF and PTF files.
2.3.1 Sequential Format
A software product kit created in sequential format is a single file whose name is in the following format:
Note that the file name is constructed of components delimited by hyphens (-). The version component is further divided into subfields and includes an additional hyphen as explained in Section 2.3.5.