HP OpenVMS Systems Documentation

Content starts here

POLYCENTER Software Installation Utility Developer's Guide


Previous Contents Index


Chapter 7
Product Description Language Statements

This chapter describes the individual Product Description Language (PDL) statements and functions.

7.1 PDL Evolution

The POLYCENTER Software Installation utility is an integrated component of OpenVMS Version 6.1 and later. After its introduction, subsequent releases of the OpenVMS operating system have incorporated various enhancements to PDL statements and functions. It is likely that we will make further enhancements over time.

Earlier versions of the OpenVMS operating system do not support the new utility features provided in later versions of the operating system. This creates a challenge for the developer who must devise a kit that will install as expected in a variety of customer environments.

You can write a product description file based on the earliest version of OpenVMS at your customer sites. If you choose this approach, you must have or acquire knowledge about customer environments. It means you can use only the statements and functions (and their parameters and options) available for the earliest customer installed version of OpenVMS.

Another option you have is to require your customers to apply a software patch kit, available from Hewlett-Packard, that back ports utility functionality to earlier versions of OpenVMS. With this strategy, you can use the latest utility enhancements in your product installation.

Table 7-1 and Table 7-2 let you quickly see when new utility features were made available. Note that bug fixes are not shown unless they impact the behavior of the utility. For more information on a specific feature, see the appropriate section in this manual.

\\New option: interactive
New logical name: PCSI$DESTINATION\)

Table 7-1 Features by OpenVMS Version: Statements
PDL Statements OpenVMS V7.1 OpenVMS V7.1-2(Alpha)
OpenVMS V7.2(VAX)
OpenVMS V7.3
APPLY TO   New option: version above  
BOOTSTRAP BLOCK     Obsolete: not available for layered products
ERROR New option: abort New behavior: performs action before the configuration dialog, when possible  
EXECUTE ABORT   New statement  
EXECUTE INSTALL...REMOVE   New option: interactive  
EXECUTE POSTINSTALL   New option: interactive New behavior: runs also on reconfigure operation
EXECUTE PRECONFIGURE   New statement  
EXECUTE REBOOT   New statement  
EXECUTE RELEASE   New option: interactive Obsolete: new kits should use EXECUTE UPGRADE or other EXECUTE statements
EXECUTE START...STOP      
EXECUTE TEST   New option: interactive
New logical name: PCSI$DESTINATION
 
EXECUTE UPGRADE     New statement
FILE   New behavior: supports intraproduct conflict detection New behavior: file from kit selected to resolve conflict on non-zero generation number tie
INFORMATION New option: with helptext    
MODULE   New behavior: supports intraproduct conflict detection New behavior: module from kit selected to resolve conflict on non-zero generation number tie
OPTION New option: with helptext    
PATCH IMAGE     Obsolete: new kits should use FILE statement to replace file
PATCH TEXT     Obsolete: new kits should use FILE statement to replace file
SOFTWARE   New option: version above  
UPGRADE   New option: version above  

Table 7-2 Features by OpenVMS Version: Functions
Function OpenVMS V7.1 OpenVMS V7.1-2(Alpha)
OpenVMS V7.2(VAX)
OpenVMS V7.3
LOGICAL NAME   New function  
SOFTWARE   New behavior: detects whether or not a patch or mandatory update kit has been installed
New options:
installed before
installed after
kit accessible
version above
 
UPGRADE   New option: version above New behavior: version range checking fully supported

7.2 PDL Conventions

The PDL conventions used are described in the Preface. However, the syntax descriptions in this chapter make significant use of several conventions, and they are worth repeating here:

  • Brackets ([ ]) indicate optional elements. You can choose one, none, or all of the options.
  • Braces ({ }) indicate a required choice of options; you must choose one of the options listed.
  • The vertical bar (|) separates optional elements. It functions as a logical OR between two options, as in A | B , or A | B | C .
  • Horizontal ellipsis points ( ... ) in examples indicate that the preceding item or items can be repeated one or more times, or that additional parameters, values, or other information can be entered.
  • The semicolon (;) in syntax diagrams is required syntax.
  • Angle brackets (<>) in syntax diagrams are required syntax.
  • A double hyphen (- rest of the line is a comment.
  • Unless otherwise indicated, extra space and tab characters may be used freely between syntax elements for the purposes of formatting and readability.
  • A statement may span more than one line.

Note

The space is required between the [NO] qualifier and its option, for example [NO] ACCESS CONTROL. This differs from standard DCL syntax.


Previous Next Contents Index