Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services software patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_PCSI-V0100 Alpha V7.3 PCSI ECO Summary
TITLE: OpenVMS VMS73_PCSI-V0100 Alpha V7.3 PCSI ECO Summary
 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
 
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
 
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.
 

New Kit Date:       28-JUN-2003
Modification Date:  Not Applicable
Modification Type:  New Kit

Copyright (c) Hewlett-Packard Company 2003.  All rights reserved.

OP/SYS:     OpenVMS Alpha

COMPONENT:  PCSI

SOURCE:     Hewlett-Packard Company

ECO INFORMATION:

     ECO Kit Name:  VMS73_PCSI-V0100
                    DEC-AXPVMS-VMS73_PCSI-V0100--4.PCSI
     ECO Kits Superseded by This ECO Kit: None  
     ECO Kit Approximate Size:  4208 Blocks
     Kit Applies To: OpenVMS Alpha V7.3
     System/Cluster Reboot Necessary:  NO
     Rolling Re-boot Supported:  NONE
     Installation Rating:  
                            1 : To be installed by all customers.
           		

     Kit Dependencies:

       The following remedial kit(s), or later, must be installed BEFORE
       installation of this , or any required kit:

         None.

       In order to receive all the corrections listed in this
       kit, the following remedial kits, or later, should also be installed:

         None 


ECO KIT SUMMARY:

An ECO kit exists for System components on OpenVMS Alpha V7.3.  
This kit addresses the following problems:

NEW FUNCTIONALITY INCLUDED IN THE VMS73_PCSI-V0100 KIT

     o  Perform installation and reconfiguration operations in
        recovery mode.

        This patch kit implements a new /RECOVERY_MODE qualifier.
        When installing a patch or full type kit in recovery mode, if
        the operation is terminated (either due to an error condition
        or by the user entering CTRL-C or CTRL-Y), any files that were
        added, modified, or deleted by the kit installation are
        restored to their state prior to the operation.  The
        /RECOVERY_MODE qualifier enables recovery mode for the PRODUCT
        INSTALL and PRODUCT RECONFIGURE commands.

        The /RECOVERY_MODE qualifier allows you to recover from a
        failed installation of any type of kit.  Once the operation
        completes, the recovery data is automatically deleted.

                            *** Note ***

        All current OpenVMS operating system patch kits support this
        new /RECOVERY_MODE capability.  However, operating system
        patch kits that are no longer current and/or some current
        layered product patch kits may not support /RECOVERY_MODE.  If
        such a kit is installed using the /RECOVERY_MODE qualifier
        PCSI may not be able to correctly perform a recovery, leaving
        your system in an inconsistent state.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE

     o  Uninstallation of Patch kits

        This patch kit gives the user the capability to uninstall
        (UNDO) patch kits for which recovery data has been saved.
        This capability is supported by the following new commands:

           o  PRODUCT INSTALL /SAVE_RECOVERY_DATA

           o  PRODUCT UNDO PATCH

           o  PRODUCT SHOW RECOVERY_DATA

           o  PRODUCT DELETE RECOVERY_DATA

        There are several constraints to using this functionality that
        the user should be aware of:

           -  A patch must be installed using the /SAVE_RECOVERY_DATA
              qualifier in order to create a recovery data set for use
              at the time the kit is uninstalled.  Each PRODUCT INSTALL
              /SAVE_RECOVERY_DATA command creates a separate recovery
              data set that will contain information about one or more
              patches.

           -  Patches can only be uninstalled in the reverse order in
              which they were installed.  You can "UNDO" the last patch
              installed, then the previous one, etc.

           -  Once there is recovery data on the system, if a patch kit
              is installed without the /SAVE_RECOVERY_DATA qualifier,
              recovery data for all patch kits that had been installed
              using the /SAVE_RECOVERY_DATA qualifier will be lost.
              However, the user will be notified by any patch
              installation that will delete recovery data and will be
              given the opportunity to cancel the installation before
              any data is deleted.

           -  Any installation of a non-patch kit, for example a layered
              product kit, will delete all recovery data sets that may
              have been created during previous patch installations.
              However, the user will be notified by any installation
              that will delete recovery data and will be given the
              opportunity to cancel the installation before any data is
              deleted.

           -  The PRODUCT UNDO PATCH command is not related to the
              PRODUCT REMOVE command that is used to uninstall full
              products.

           -  All current OpenVMS operating system patch kits support
              this new UNDO mode capability.  However, operating system
              patch kits that are no longer current and/or some current
              layered product patch kits may not support UNDO mode.  If
              such a kit is installed using the PRODUCT INSTALL
              /SAVE_RECOVERY_DATA command and then uninstalled using
              PRODUCT UNDO PATCH, your system may be left in an
              inconsistent state.


        Consult the on-line help text for more information about the
        patch removal capability.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  PRODUCT SHOW OBJECT command enhanced to show the generation
        number

        The PRODUCT SHOW OBJECT command has been enhanced to show the
        generation number associated with each file and module
        installed.  A generation number is a attribute of certain
        objects that is used by the POLYCENTER Software Installation
        utility to resolve conflicts when two or more products provide
        the same file or library module.  See the on-line help text
        for the PRODUCT SHOW OBJECT command to learn more about
        generation numbers.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  Implementation the /FULL qualifier of the PRODUCT LIST
        command.

        The /FULL qualifier has been added to the PRODUCT LIST
        command.  This qualifier provides file size and other useful
        information.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  Implementation of the EXECUTE UPGRADE statement

        The EXECUTE UPGRADE statement has been added to the product
        description language for creating product description files.
        This statement allows product kit developers to specify that a
        command procedure be executed only when the product is being
        upgraded.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  Improved handling of files with the same generation number.

        If a file or library module from a product kit being installed
        has the same generation number attribute as an object with the
        same name already installed by another product (or another
        patch for the same product), the file or module from the kit
        will be installed.  Previously, the file or module already
        installed was retained.  This change ensures that the
        re-installation of a full product or patch will cause objects
        from the kit to be re-copied to the system.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  Enable the use of compressed kits

        The PRODUCT INSTALL command can operate on PCSI kits with a
        file type of .PCSI$COMPRESSED in a transparent manner.
        Compressed kits are encoded using a data compression technique
        that significantly reduces their file size.  When a compressed
        kit is installed, records are decompressed (expanded)
        on-the-fly so no additional disk space is required to store a
        decompressed version of the kit.  Full support for creating
        and manipulating compressed kits is expected to be available
        in the next release for OpenVMS Alpha.  This remedial kit
        enables the use of compressed kits when they become available
        in the future.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


PROBLEMS ADDRESSED IN VMS73_PCSI-V0100 KIT

     o  "Software Reference data is not available" error message

        An attempt to remove a software product terminates with the
        following error message:

          %PCSI-E-NOSOFREF, Software Reference data is not
          available
          %PCSI-E-S_OPFAIL, operation failed %PCSI-E-ABOARD,
          operation terminated due to an unrecoverable error-con.

        This error can occur when a software product is removed that
        has an optional reference to another product, but that option
        was not selected when the product was installed.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE



     o  Partial product kit problems corrected

        Several obscure problems related to partial product kits have
        been resolved.  In general, these problems were related to
        operations performed after a partial kit had been successfully
        installed.  These problems included failures in:

          1.  Installing a full product kit with a lower version than
              that of a partial kit for the same product

          2.  Downgrading a platform product that included a partial
              kit.

        This also fixes a product database corruption problem.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE




     o  $SS_NOLOGNAM error on patch kit installation

        Use of the PDL statement EXECUTE START...STOP INTERACTIVE in a
        patch kit causes the installation of the patch kit to fail
        with an $SS_NOLOGNAM error.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE



     o  FILE statements enclosed in a REMOVE group do not always
        remove the specified files.

        In a product description language file for a patch kit, FILE
        statements enclosed in a REMOVE group nested in an IF-ELSE
        group do not always remove the specified files.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE



     o  Files related to a particular product option are not removed

        When a product is installed with an option selected and then
        subsequently reinstalled with the option deselected, the files
        for that option are not removed.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  Cannot install a product that has a software reference to
        another product

        A product that has a software reference to another product can
        not be installed if that other product does not allow an
        upgrade to itself.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE




     o  Build ident field not updated with an encoded generation
        number

        At installation, when the SOURCE option on a FILE statement in
        a PDF refers to a file that is not a .EXE file, the build
        ident field of an Alpha image is not updated with an encoded
        generation number.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE




     o  User can continue patch installation when wrong version of the
        product is installed.

        PCSI allows the user to continue the installation of a patch
        kit when the wrong version of the product to which the patch
        applies is installed.  This fix prevents installation of the
        patch.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE



     o  Provide better explanations when /DESTINATION qualifier is
        ignored.

        Provide better explanations to the user when the /DESTINATION
        qualifier of the PRODUCT INSTALL command is purposely ignored.
        This occurs when the same version of a product is re-installed
        or a patch is applied to an installed product.  In these cases
        the destination cannot be changed.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE



     o  Illegal PDL SOFTWARE statements that refer to another patch
        kit are not caught.

        Installation of a patch kit that contains a PDL SOFTWARE
        statement that refers to another patch kit fails with an
        ACCVIO.  This fix enforces a restriction against such
        statements.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE




     o  PRODUCT PACKAGE operation does not fail when USES option
        files are missing

        The PRODUCT PACKAGE operation does not abort when a file
        specified in the USES option of an EXECUTE statement is not
        found.  With this fix the PACKAGE operation will abort.  All
        missing files will be identified before the operation
        terminates.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE



     o  On reinstallation verify that the kit provides the same
        objects as were originally provided.

        On reinstallation of a product, verify that the kit provides
        the same objects as were originally provided when the product
        was first installed.

        During the kit development process, product developers may add
        or delete objects from their kit but fail to change the
        version of the kit.  This can result in unintended behavior
        when installing the new kit and in certain cases may lead to
        product database corruption.  This happens because
        reinstallation of the same version of a product is assumed to
        be a replacement operation and certain optimizations are
        utilized in the processing of the kit.  With this change, the
        POLYCENTER Software Installation utility compares the list of
        objects previously installed with the objects listed in the
        new kit to verify that there is a one-to-one correspondence.
        If not, the developer is notified of the discrepancy.

        Images Affected:[SYSEXE]PCSI$MAIN.EXE
                        [SYSLIB]PCSI$SHR.EXE



     o  PCSI database corruption

        In the following scenario, product database corruption will
        occur.  The corruption is caused by improper processing of a
        DIRECTORY statement in the product description file:

          1.  A full product is installed that explicitly creates
              directories [A] and [A.B.C]

          2.  A patch kit is then installed that explicitly creates
              directory [A.B]

          3.  The full product is upgraded


        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  PRODUCT command aborts on deallocation of virtual memory

        Under certain conditions, the PRODUCT command aborts on
        deallocation of virtual memory.  This is most likely to occur
        when the destination device for an installation contains many
        access control lists.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  Insufficient error message when spawn of a subprocess fails

        If during the execution of a PRODUCT INSTALL command, an
        attempt to spawn a subprocess fails or an attempt to create a
        detached subprocess fails, the primary error message is not
        reported - just a generic PCSI abort message is displayed.
        With this change, the primary error message is now reported.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE



     o  Various problems related to PRODUCT EXTRACT RELEASE_NOTES

        Fix Various problems related to PRODUCT EXTRACT RELEASE_NOTES:

           o  Preserve the file name of a release notes file on
              extraction instead of giving it the name of
              DEFAULT.PCSI$RELEASE_NOTES.

           o  If there is more than one release notes file in a product
              kit, because they may be in different formats such as
              .TXT, .HTML, and PS, extract them as separate files
              instead of concatenating them.

           o  Support sequential files in VFC format as release notes.


        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE




     o  Many informational, warning, and error messages have been
        added or revised.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE


     o  ACCVIO when multiple patch kits installed provide same file
        with the same generation number.

        An ACCVIO occurs when multiple patch kits are installed and
        two or more of these kits provide the same file with the same
        generation number.

        Images Affected: [SYSEXE]PCSI$MAIN.EXE
                         [SYSLIB]PCSI$SHR.EXE

INSTALLATION NOTES:

No reboot is necessary after successful installation of the kit.
However, users will need to log out and log back in in order to use
the new PCSI features.

INSTALLATION INSTRUCTIONS:

Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:

    PRODUCT INSTALL VMS73_PCSI /SOURCE=[location of Kit]

The kit location may be a tape drive, CD, or a disk directory that
contains the kit.

Additional help on installing PCSI kits can be found by typing
    HELP PRODUCT INSTALL at the system prompt


Special Installation Instructions:

     o  Scripting of Answers to Installation Questions

        During installation, this kit will ask and require user
        response to several questions.  If you wish to automate the
        installation of this kit and avoid having to provide responses
        to these questions, you must create a DCL command procedure
        that includes the following definitions and commands:

           -  $ DEFINE/SYS NO_ASK$BACKUP TRUE

           -  Add the following qualifiers to the PRODUCT INSTALL
              command and add that command to the DCL procedure.

                /PROD=DEC/BASE=AXPVMS/VER=1.0

           -  De-assign the logicals assigned

        For example, a sample command file to install the
        VMS73_PCSI-V0100 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $!
          $ PROD INSTALL VMS73_PCSI/PROD=DEC/BASE=AXPVMS/VER=1.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $!
          $ exit


All trademarks are the property of their respective owners.
 
Files on this server are as follows:
»dec-axpvms-vms73_pcsi-v0100--4.README
»dec-axpvms-vms73_pcsi-v0100--4.CHKSUM
»dec-axpvms-vms73_pcsi-v0100--4.pcsi-dcx_axpexe
privacy statement using this site means you accept its terms