[an error occurred while processing this directive]

HP OpenVMS Systems Documentation
Content starts here

POLYCENTER Software Installation Utility Developer's Guide

Previous Contents Index

Statement

In a full, platform, or operating system PDF, the UPGRADE statement is optional. When present, the UPGRADE statement specifies the versions of the product that can be successfully upgraded by the product kit. If a version of the product is currently installed but does not meet the version selection criteria in the UPGRADE statement, the installation is terminated. The UPGRADE statement has no effect when the product is being installed for the first time. If an UPGRADE statement is not present in the PDF, the kit being installed is allowed to upgrade (or replace) any version of the product that might be installed. This includes a lower version, a higher version, or the same version of the product.

In a partial PDF, the UPGRADE statement is required. The statement specifies which versions of the product must be installed for the partial kit to be applied successfully.

You cannot use the UPGRADE statement for a patch, mandatory update, or transition PDF.

Function

The UPGRADE function tests whether a version of the product in the specified range is being upgraded by the current operation. If a version of the product in the specified range is currently installed, the function returns true; otherwise it evaluates to false. If no range is given, the function tests whether any version of the product is currently installed.

The UPGRADE function is not meaningful for a patch, mandatory update, or transition PDF. If included in these PDFs, the UPGRADE function always evaluates to false. See Also APPLY TO
IF
PRODUCT
SOFTWARE

Examples

#1 

product HP AXPVMS ABC V4.0 full ;
    upgrade version minimum V2.0 ;
   .
   .
   .
end product ;

The UPGRADE statement in this example does not allow product ABC V4.0 to upgrade versions of the product prior to V2.0. Product ABC, however, can upgrade to V2.0 or later of the product. Or, if a previous version of the product is not currently installed, it can perform a new installation.

#2 

product HP AXPVMS DEF V4.2 partial ;
    upgrade version required V4.1 ;
   .
   .
   .
end product ;

The UPGRADE statement in this PDF is required because this is a partial kit. It specifies that product DEF V4.1 must already be installed in order to apply this partial kit to upgrade the product to V4.2.

#3 

product HP VAXVMS JKL V2.5 full ;
    if (<upgrade>) ;
    information UPG_MSG ;
    end if ;
   .
   .
   .
end product ;

In this example, if any version of product JKL is currently installed, an informational message will be displayed to the user.

#4 

product HP VAXVMS JKL V2.5 full ;
    if (<upgrade version minimum A1.0 version below A2.0>) ;
    file [sysupd]jkl_convert.com ;
    end if ;
   .
   .
   .
end product ;

If version 1 of the product (from beta test through final release) is being upgraded, the UPGRADE function in this PDF is used to conditionally provide a file.

Appendix A
Migrating from VMSINSTAL to the POLYCENTER Software Installation Utility

VMSINSTAL is an installation mechanism supplied by Hewlett-Packard. This appendix contains information about VMSINSTAL options and callbacks and their POLYCENTER Software Installation utility equivalents.

A.1 VMSINSTAL Options and Equivalents

Table A-1 lists some tasks that you may need to perform, the corresponding VMSINSTAL option, and the POLYCENTER Software Installation utility equivalent. Note that some VMSINSTAL options do not have an equivalent. In many cases, this is because the design of the POLYCENTER Software Installation utility eliminates the need for an equivalent.

Table A-1 VMSINSTAL Options and Equivalents
Task VMSINSTAL Option POLYCENTER Software Installation Utility Equivalent
Creating a file that specifies answers to installation questions OPTIONS A Create a product configuration file (PCF). This is similar to an auto-answer file in VMSINSTAL.
Specifying a temporary work directory OPTIONS AWD Specify the /WORK qualifier to the PRODUCT command.
Starting the system OPTIONS B 1 No equivalent.
Tracing callbacks during installation OPTIONS C 2 Use the /LOG and /TRACE qualifiers on the PRODUCT INSTALL command.
Manipulating product kits OPTIONS G Use the PRODUCT COPY/FORMAT=keyword command to convert a kit into a different format (see Chapter 5).
Suppressing VMSINSTAL prompts OPTIONS I 2 Use the /OPTIONS=NOCONFIRM qualifier.
Debugging a kit OPTIONS K 2 Use the /LOG and /TRACE qualifiers to assist in debugging a PDF.
Providing a log of installation operations OPTIONS L Use the /LOG and /TRACE qualifiers. This provides more information than OPTIONS L with VMSINSTAL.
Displaying or printing release notes OPTIONS N Use the RELEASE NOTES option to the FILE statement and the PRODUCT EXTRACT RELEASE_NOTES command. The release notes are created in the current directory, using the file's original specification as the default name.
Performing an installation in test mode OPTIONS Q 2 No equivalent.
Installing a product in an alternate root OPTIONS R Use the /DESTINATION qualifier or a logical name, PCSI$DESTINATION, defined before product installation.
Pausing the installation at various points OPTIONS RSP 2 No equivalent.
Compiling information about the installation OPTIONS S 2 Use the /LOG and /TRACE qualifiers to the PRODUCT command.
1OpenVMS startup use only
2Developer's use only

A.2 VMSINSTAL Callbacks and Equivalents

To install a product using VMSINSTAL, you create a command procedure named KITINSTAL.COM that makes callbacks to VMSINSTAL. If you are migrating from VMSINSTAL to the POLYCENTER Software Installation utility, see Table A-2, which lists the VMSINSTAL callbacks and their equivalents.

Table A-2 VMSINSTAL Callbacks and Equivalents
Task VMSINSTAL Callback Option POLYCENTER Software Installation Utility Equivalent
Adding an identifier to the rights database ADD_IDENTIFIER   Use the RIGHTS IDENTIFIER statement.
Prompting the installer for information ASK   To confirm the completion of preinstallation tasks, use the CONFIRM option to the INFORMATION statement. The product text file (PTF) contains the prompt and help text.
Not recording responses to installation questions   A No equivalent.
Forcing a Boolean answer   B No equivalent.
Preceding a prompt with blank line   D No equivalent.
Disabling terminal echo   E No equivalent.
Displaying help text before the prompt   H The INFORMATION statement.
Requiring an integer as the answer   I No equivalent.
Returning input in lowercase   L No equivalent.
Returning input in the same case   M No equivalent.
Indicating a null response is acceptable   N No equivalent.
Ringing the terminal bell before the prompt   R No equivalent.
Indicating the response can be a string   S No equivalent.
Returning input in uppercase   U No equivalent.
Indicating the response can be Ctrl/Z   A No equivalent.
Determining whether a license for the product is installed on the system CHECK_LICENSE   No equivalent. License management is outside the domain of the utility.
Determining whether the network is running CHECK_NETWORK   No equivalent. If you use a statement that references the DECnet network, the utility ensures that the network is available.
Determining whether there is sufficient disk space on the target device CHECK_NET_UTILIZATION   No equivalent. The utility ensures that sufficient disk space is available.
Determining whether a minimum version of software is present in the execution environment CHECK_PRODUCT_VERSION   Use the VERSION MINIMUM option to the SOFTWARE function.
Limiting an installation to specified versions of the OpenVMS operating system CHECK_VMS_VERSION   Use the VERSION MINIMUM and VERSION MAXIMUM options to the SOFTWARE function, specifying HP as the producer name, VAXVMS or AXPVMS as the base, and VMS as the product name.
Determining which is the most recent version of an image COMPARE_IMAGE   You can manage file versions using the generation option to the FILE statement.
Determining whether the user has loaded the license for the product being installed on the system CONFIRM_LICENSE   No equivalent. License management is outside the domain of the utility.
Providing for orderly exit from an installation CONTROL_Y   No equivalent necessary; the utility provides this automatically.
Creating an account on the system CREATE_ACCOUNT   Use the ACCOUNT statement.
Deleting obsolete files from a previous installation DELETE_FILE   In full and operating system kits, the utility deletes files that are replaced during an upgrade. However, in a partial kit, you can remove obsolete files using the REMOVE statement.
Locating files FIND_FILE   If you want to determine whether an optional software product is available, use the SOFTWARE function. You do not need to determine whether a file is present before performing an operation that references it; the utility does this automatically.
Generating structure definition language (SDL) definition files GENERATE_SDL   No equivalent.
Extracting the image file identification string for a file GET_IMAGE_ID   If you want to determine the available version of a software product, use the SOFTWARE function.
Obtaining a password for an account GET_PASSWORD   No equivalent necessary; the utility provides this function.
Placing requirements on system parameters GET_SYSTEM_PARAMETER   Use the SYSTEM PARAMETER statement.
Displaying messages to the user MESSAGE   Use the INFORMATION statement to display information about pre- and postinstallation tasks. You do not need to provide error messages and progress information; the utility does this automatically.
Patching an image as part of the installation PATCH_IMAGE   No equivalent. Use the FILE statement to provide the modified file.
Moving a shareable image's symbol table to the system shareable image library when the patch is complete   I No equivalent necessary. The IMAGE LIBRARY option to the FILE statement controls its replacement in the image library.
Creating a journal file of patches   J No equivalent.
Saving old versions of the image file   K No equivalent necessary. The utility deletes existing versions.
Moving the file to the SYS$SPECIFIC directory   O No equivalent necessary. The placement of the FILE statement that originally described the image within a scope group determines its placement.
Reinstalling the image when the patch is complete   R No equivalent necessary; the utility does this automatically.
Queuing a print job to SYS$PRINT PRINT_FILE   No equivalent.
Invoking a command procedure of product-specific callbacks PRODUCT   No equivalent.
Adding a command to the system DCL table PROVIDE_DCL_COMMAND   Use the MODULE statement with the TYPE COMMAND parameter. You do not need to reinstall the system command table as a known image; the utility does this automatically.
Adding help to the DCL help library PROVIDE_DCL_HELP   Use the MODULE statement with the TYPE HELP parameter.
Adding a new file to the system PROVIDE_FILE   Use the FILE statement.
Adding a new image to the system PROVIDE_IMAGE   Use the FILE statement. The utility can distinguish whether a file is a valid executable image.
Placing the file in more than one location   C No equivalent necessary.
Dynamically patching ECOs into the new image file   E No equivalent necessary. You should package the file with the correct ECO numbers already set.
Moving a shareable image's symbol table to the system shareable image library   I Use the IMAGE LIBRARY option to the FILE statement.
Preserving old versions   K No equivalent necessary. The utility deletes existing versions.
Moving the file to the SYS$SPECIFIC directory   O Enclose the FILE statement in a SCOPE PROCESSOR group.
Specifying an input file that contains a list of logical names for the source image files and their respective destinations   T No equivalent necessary. Use one FILE statement for each file.
Changing the file name and file type of all versions of a file RENAME_FILE   Use the archive option of the FILE statement to preserve an existing version of a file during an upgrade.
Restoring save sets of a product that is divided among several save sets RESTORE_SAVESET   No equivalent necessary.
Running an image during installation RUN_IMAGE   Use the EXECUTE statement or the ASSEMBLE EXECUTE option to the FILE statement.
Specifying a UIC or protection code for product files SECURE_FILE   Use the OWNER and PROTECTION options to the DIRECTORY and FILE statements.
Modifying the access control list (ACL) of a device, directory, or file SET ACL Use the ACCESS CONTROL option of the FILE and DIRECTORY statements.
Determining the default case (upper or lower) in which text from the installer is returned to the installation procedure SET ASK_CASE No equivalent.
Running an installation verification procedure (IVP) SET IVP No equivalent necessary. You can specify the EXECUTE TEST statement and invoke the functional test for a product with the /TEST qualifier to the PRODUCT INSTALL command.
Calling a product's installation procedure after files have been moved to their target directories SET POSTINSTALL Depending on your application, you can use the EXECUTE POSTINSTALL statement.
Purging files replaced by an installation SET PURGE No equivalent necessary. The utility deletes existing versions.
Rebooting the system after the installation SET REBOOT Use the EXECUTE REBOOT statement.
Ensuring a high level of installation success SET SAFETY No equivalent necessary. The utility provides the necessary disk management and reliability features.
Rebooting the system after the installation SET SHUTDOWN Use the EXECUTE REBOOT statement.
Specifying a product-specific startup command procedure SET STARTUP Use the EXECUTE START statement.
Editing text files SUMSLP_TEXT   No equivalent. Use the FILE statement to provide the modified file.
Identifying installation peculiarities TELL_QA   No equivalent necessary.
Exiting the installation procedure UNWIND   No equivalent necessary. The utility controls the flow of the installation.
Updating an existing user account UPDATE_ACCOUNT   Use the ACCOUNT statement to modify existing user accounts.
Making a file available for updating by copying it to a working directory UPDATE_FILE   No equivalent necessary.
Modifying an identifier in the rights database UPDATE_IDENTIFIER   Use the RIGHTS IDENTIFIER statement to modify an existing rights identifier.
Updating a library UPDATE_LIBRARY   Use the MODULE statement with the appropriate parameter for the type of library you are updating. To update the shareable image library, use the IMAGE LIBRARY option to the FILE statement. No equivalent exists to update RSX libraries.

Previous Next Contents Index