*******************************************************************************
* *
* This is a newly released patch... *
* *
* Online links can be found at *
* http://ftp.support.compaq.com/patches/public/vms/vax/v7.2/dec-vaxvms-vms72_pcsi-v0100--4.README
*******************************************************************************

TITLE: OpenVMS VMS72_PCSI-V0100 VAX V7.2 PCSI ECO Summary
 
New Kit Date : 04-APR-2001
Modification Date: 07-APR-2001
Modification Type: DOCUMENTATION: Note added regarding Kit Dependencies

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-dcx_axpexe.pcsi, then it can
       be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
       file will be the PCSI installation file which can be used to install
       the ECO.
 
Copyright (c) Compaq Computer Corporation 2001. All rights reserved.

OP/SYS: OpenVMS VAX

COMPONENT: PCSI

SOURCE: Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name: VMS72_PCSI-V0100
                    DEC-VAXVMS-VMS72_PCSI-V0100--4.PCSI
     ECO Kits Superseded by This ECO Kit: None
     ECO Kit Approximate Size: 1824 Blocks
     Kit Applies To: OpenVMS VAX V7.2
     System/Cluster Reboot Necessary: No
     Rolling Re-boot Supported: Not Applicable
     Installation Rating: INSTALL_1
                           1 - To be installed by all customers.

     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:

         None

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

         None
   
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    X X
    X NOTE: The VAXUPDATE01_072 kit should be installed first X
    X BEFORE installation of this kit. X
    X X
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

ECO KIT SUMMARY:

An ECO kit exists for PCSI on VAX V7.2. The new kit addresses
the following problems:

PROBLEMS ADDRESSED IN VMS72_PCSI-V0100 KIT:

  o When installing FORTRAN and FORRTL products, the system hangs
     if both products are selected for installation at the same
     time.

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

  o If the following PCSI steps are taken:

     1. Install a FULL type product kit

     2. Patch the FULL product with a PATCH type kit(s)

     3. Install a PARTIAL type software product on top of the FULL
         kit

     then, two versions of the same FULL product are created and

     patches are not transferred from the FULL product to the
     PARTIAL product. This would eventually lead to an
     un-repairable PCSI database corruption.

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

  o The following duplicate error messages reported by the PCSI
     utility display during a product upgrade:

     %PCSI-E-INSVOLSPC, insufficient space on volume DISK$ALPCSI_SYS
     -PCSI-I-VOLSPC, 159261 required; 124344 available; -34917 net
     Terminating is strongly recommended.
     Do you want to terminate? [YES] no

     %PCSI-E-INSVOLSPC, insufficient space on volume DISK$ALPCSI_SYS
     -PCSI-I-VOLSPC, 159261 required; 124344 available; -34917 net
     Terminating is strongly recommended.
     Do you want to terminate? [YES] no

         Images Affected: [SYSLIB]PCSI$SHR.EXE

  o The reinstallation of a PARTIAL kit causes an ACCVIO. This
     occurs when certain data is passed from one instance of the
     PARTIAL product to another instance of the same product.
     After the transfer, pointers to the originating data
     structures are cleared. These pointers will be needed later.

     When the PARTIAL kits are different, re-installation of
     PARTIAL kit will not clear pointers.

         Images Affected: [SYSLIB]PCSI$SHR.EXE

  o When re-installing a product that has a library module in its
     Product Description File (PDF), the PCSI utility terminates
     with an ACCVIO error.

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

  o Changed the behavior of file conflict resolution between a
     file from the kit being installed and a file with the same
     name that has already been installed. Previously, when two
     files had the same generation number, the PCSI utility would
     retain the file already on the system disk. Now when there is
     a tie, the file from the kit being installed replaces the file
     previously installed.

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

  o When a PRODUCT RECONFIGURE command is executed and the
     re-configured product has two or more patches applied to it,
     the PCSI utility incorrectly marks the patches as removed.
     This inconsistency can cause an ACCVIO on subsequent
     operations.

         Images Affected: [SYSLIB]PCSI$SHR.EXE

  o When a FULL product kit replaces a file provided by another
     product, or a PATCH product kit replaces a file provided by
     its parent product or another patch, use of the IMAGE LIBRARY
     option of the FILE statement in the PDF (Product Description
     File) must be used consistently. For example, if one product
     provides a file and places it in SYS$LIBRARY:IMAGELIB.OLB, but
     another product replaces the file but does not specify that it
     should also be placed in image library, then the installation
     will fail with a %PCSI-E-PARUDF error message.

         Images Affected: [SYSLIB]PCSI$SHR.EXE

  o An attempt to upgrade a product and also apply a patch (or
     ECO) kit to it in the same PRODUCT INSTALL opertion may fail
     with the following error:

         %PCSI-E-FAILCONF, ...

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

  o Installation of two or more patch kits that provide the same
     file, and also update IMAGELIB.OLB with the file, may cause
     the PCSI product database to be inconsistent if the patch kits
     are installed out of order. Symptons include:

       o Output from a PRODUCT SHOW OBJECT /FULL command shows that
          all versions of the file are in conflict with one another
          (i.e., no file in the set has a status of "OK").

       o Output from a PRODUCT SHOW OBJECT /FULL command shows that
          the owner of the file is one product and the owner of the
          module in IMAGELIB.OLB is another product (or patch).

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

  o When a number of patch kits are installed in a descending
     version sequence, and they contain files with IMAGE LIBRARY
     attribute set, a PRODUCT SHOW OBJECT command will display all
     the IMAGE LIBRARY files at conflict. This indicates incorrect
     entries to the PCSI database and may cause some problems.

         Images Affected: [SYSLIB]PCSI$SHR.EXE

INSTALLATION NOTES:

The system does not need to be rebooted after this kit is installed.
However, all processes will need to log out and then back in to use
the new PRODUCT command qualifiers and keywords.

All trademarks are the property of their respective owners.

---

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]