hp.com home products and services support and drivers solutions how to buy
cd-rom home
End of Jump to page title
HP OpenVMS systems

Jump to content

POLYCENTER Software Installation Utility Developer's Guide

POLYCENTER Software Installation Utility Developer's Guide

Previous Contents Index

5.5.3 Converting a Sequential Kit into Reference Format

You can use the PRODUCT COPY command to extract files from a kit in sequential format and place them in reference format. This differs in a number of ways from extracting all files from a sequential kit into a specific directory using the PRODUCT EXTRACT FILE command. When copying a kit into reference format, the files are placed in a directory tree as they would appear after installation on the user's system. Unlike the installation of a sequential kit, however, temporary files from the kit are placed in the directory tree and files pertaining to all options are extracted.

You can also use the PRODUCT COPY command to convert a reference kit into sequential format, and for copying a kit while preserving its format.

5.5.4 Converting a Sequential Kit into Compressed Format

You can use the PRODUCT COPY command to convert a sequential kit into compressed format. The following example illustrates this technique:


The /SOURCE qualifier points to the location of the sequential kit you want to convert to the compressed format. The /DESTINATION= qualifier points to the location where the newly-created compressed kit will reside.

5.6 Displaying Information from the Product Database

After the product kit is installed, you can use the PRODUCT SHOW PRODUCT command to list the products installed on the system. Use the /FULL qualifier for additional information about software references and patches that may have been applied to the products. Additional commands (not shown here) that are useful for obtaining more information about installed products are the PRODUCT SHOW HISTORY /FULL, PRODUCT SHOW OBJECT /FULL, and PRODUCT SHOW RECOVERY_DATA commands.

$ PRODUCT INSTALL CHESS  ! /LOG and /TRACE are useful for debugging 
----------------------------------- ----------- ------------ 
PRODUCT                             KIT TYPE    STATE 
----------------------------------- ----------- ------------ 
ABC_CO AXPVMS CHESS V1.0            Full LP     Installed 
DEC AXPVMS DECNET_PHASE_IV V7.1     Full LP     Installed 
DEC AXPVMS DWMOTIF V1.2-4           Full LP     Installed 
DEC AXPVMS VMS V7.1                 Transition  Installed 
----------------------------------- ----------- ------------ 
4 items found 

Chapter 6
Advanced Topics

This chapter contains information about the following advanced POLYCENTER Software Installation utility concepts:

In addition, it presents flow diagrams depicting the execution of several PRODUCT commands.

6.1 Using Command Procedures in PDL Statements

The Product Description Language (PDL) provides statements that perform common kit installation tasks such as creating directories, copying files to the target disk, updating libraries, displaying informational messages, and so on. There are times, however, when you might need to perform tasks that are unique to your product. For example, a new version of a product might need to detect the existence of a data file from a previous version and convert it to a new format. Or, you might want to probe the operating environment or ask the user specific questions before an installation may proceed.

To support this type of customization, the PDL provides several EXECUTE statements. These statements let you include command procedures (or individual DCL commands) that run during certain phases of a product install, upgrade, reconfigure, undo patch, or remove operation. These statements are:

Table 6-1 lists the PDL statements you can use to run command procedures (or individual DCL commands) that you provide. The statements are listed in the order of their execution during an installation, reconfiguration, or remove operation. Note that the table distinguishes between a new installation and an upgrade installation. The term upgrade denotes replacement of an installed version of a product by a higher, lower, or the same version of the product.

Table 6-1 Command Procedure Execution by Operation
PDL Statements
Listed in the
Order of Execution
1st Time
EXECUTE PRECONFIGURE yes yes yes no no
EXECUTE...STOP no yes 1 no yes no
EXECUTE...REMOVE no no no yes no
EXECUTE UPGRADE no yes 1 no no no
FILE statement using ASSEMBLE EXECUTE yes yes yes 2 no no
EXECUTE INSTALL... yes yes yes no no
EXECUTE START... yes yes no no no
EXECUTE POSTINSTALL yes yes yes no no
EXECUTE TEST yes yes yes no no
EXECUTE LOGIN no 3 no 3 no 3 no no
EXECUTE START...STOP no 3 no 3 no 3 no no
EXECUTE ABORT yes 4 yes 4 yes 4 no no
EXECUTE REBOOT yes 5 yes 5 yes 5 no no
EXECUTE PRE_UNDO no no no no yes
EXECUTE POST_UNDO no no no no yes

1Only commands from the EXECUTE statement of the product being removed are run.
2The file is created only if the statement is part of a configuration option that the reconfiguration operation selects for the first time.
3The only action performed at this time is to display a message to the user.
4Commands from the EXECUTE ABORT statement are run only when an error condition causes the operation to terminate.
5Commands from the EXECUTE REBOOT statement are run if the user allows it during the operation.

Previous Next Contents Index