HP OpenVMS Systems Documentation
Content starts here

POLYCENTER Software Installation Utility Developer's Guide

Previous Contents Index

PART

The PART statement displays a message from the specified text module in the PTF about a group of statements during the configuration phase of an installation, configuration, or reconfiguration operation. The PART and END PART statements form a PART group.

Syntax

PART name ;

[ PDL-statements ]

END PART ;

Parameter

name

Indicates, as a quoted or unquoted string, the name of the associated PTF text module. The name you specify can be from 1 to 31 characters in length and must be unique among all names in the same product description.

Option

PDL-statements

Any product description language statement or a group of statements described in this reference section, except the PRODUCT and END PRODUCT statements.

Required Terminator

END PART ;

Description

The PART statement displays a message from the specified text module in the PTF about a group of statements during the configuration phase of an installation, configuration, or reconfiguration operation. You can nest PART groups, which are processed in lexical order.

Although the syntax of the part group and the option group is similar, their purpose is quite different. The part group simply displays a message and does not affect the processing of PDL statements contained within the group. In contrast, the option group prompts the user to accept or decline the option, causing the PDL statements that make up the option to be processed or ignored.

By default, the prompt text string is displayed without help text. However, help text is displayed after the prompt text when the user specifies the /HELP qualifier on the command line.

You must supply prompt text for the PART statement in the PTF using the =prompt directive. Help text is optional. If provided, it must immediately follow the prompt text line.

See Also INFORMATION
OPTION

Example

Suppose the product description file contains the following lines: 

part CSWS ;
    software HP AXPVMS CSWS
        version required V1.0 component ;
    software HP AXPVMS MOD_JSERV
        version required V1.0 component ;
    software HP AXPVMS MOD_PERL
        version required V1.0 component ;
end part;

The product text file contains the corresponding text: 


1 CSWS
=prompt HP Secure Web Server
This platform provides the following products:
* HP Secure Web Server software (Based on Apache)
* MOD_JSERV software
* MOD_PERL software

This example shows how to use the PART statement to display a message about the required software products that this platform provides.

PATCH IMAGE (VAX only)

The PATCH IMAGE statement updates an executable image using PATCH commands.

Note
As of OpenVMS Version 7.3, the PATCH IMAGE statement is obsolete. To support existing product kits that may have used this statement, the POLYCENTER Software Installation utility continues to process this statement in a backward-compatible manner. However, we recommend that you not use the PATCH IMAGE statement in new or revised product kits. Instead of patching an image file, provide a replacement image file with a FILE statement. Documentation of the PATCH IMAGE statement may be discontinued in a future release of this manual.

Syntax

PATCH IMAGE name WITH source ;

Parameters

name

Indicates the relative file specification of the executable image you want to update.

WITH source

Indicates the file specification of the file containing the update commands. The file must contain OpenVMS VAX Image File Patch Utility (PATCH) commands.

Description

The PATCH IMAGE statement updates an executable image using PATCH commands. Use this statement when it is inconvenient to provide a new image.

You must supply the file containing the update commands as part of the product material.

The PATCH IMAGE statement specifies a managed object that has the following characteristics:

  • Its name is the same as the name parameter of the product group in which the statement is lexically contained; it is a multicomponent name qualified by the relative file specification of the file that is being updated. It must be unique with respect to all managed objects in all scopes.
  • It has assembly lifetime, and its scope is the same as that of the file being updated.
  • Managed object conflict is unrecoverable.

Example


patch image [SYS$LDR]SYS.EXE with [SYSUPD]VERSION_PATCH.PAT ;

This statement provides a file, [SYSUPD]VERSION_PATCH.PAT, to patch the image [SYS$LDR]SYS.EXE.

PATCH TEXT

The PATCH TEXT statement updates a text file using SUMSLP commands.

Note
As of OpenVMS Version 7.3, the PATCH TEXT statement is obsolete. To support existing product kits that may have used this statement, the POLYCENTER Software Installation utility continues to process this statement in a backward-compatible manner. However, Hewlett-Packard recommends that you do not use the PATCH TEXT statement in new or revised product kits. If possible, provide a replacement file with a FILE statement. If this is not practical, and you must edit an existing file, consider using a FILE statement with the ASSEMBLE EXECUTE and ASSEMBLE USES options to run a command procedure that places a copy of the previously installed file in the PCSI$DESTINATION scratch directory and performs the editing function there. Documentation of the PATCH TEXT statement may be discontinued in a future release of this manual.

Syntax

PATCH TEXT name WITH source ;

Parameters

name

Indicates the relative file specification of the text file you want to update.

WITH source

Indicates the file specification of the file containing the update commands (as a single quoted or unquoted string). The file must contain SUMSLP commands for use by the EDIT/SUM editor.

Description

The PATCH TEXT statement updates a text file using SUMSLP commands. Use this statement when it is inconvenient to provide a new file.

You must supply the file containing the update commands as part of the product material. You must also supply the file that you want to update, but this file is not propagated to the product kit. The POLYCENTER Software Installation utility uses it to calculate the input and output checksum values.

The PATCH TEXT statement creates a temporary directory, identified by the logical name PCSI$SCRATCH, to compute a checksum value. The PCSI$SCRATCH directory is created as a subdirectory of SYS$SCRATCH.

The PATCH TEXT statement specifies a managed object that has the following characteristics:

  • Its name is the same as the name parameter of the product group in which the statement is lexically contained; it is a multicomponent name qualified by the relative file specification of the file that is being updated. It must be unique with respect to all managed objects in all scopes.
  • It has assembly lifetime, and its scope is the same as that of the file being updated.
  • Managed object conflict is unrecoverable.

Example


patch text [SYSUPD]VMSINSTAL.COM with [SYSUPD]VMSINSTAL.SLP ;

This statement provides a file, [SYSUPD]VMSINSTAL.SLP, to patch the text file [SYSUPD]VMSINSTAL.COM.

Previous Next Contents Index