****************************
       ECO SUMMARY INFORMATION
    ****************************

    Kit Name: VMS731_EV7-V0300
              DEC-AXPVMS-VMS731_EV7-V0300--4.PCSI
    Kit Applies To: OpenVMS ALPHA V7.3-1
    Approximate Kit Size: 22064 blocks
    Installation Rating: INSTALL_2
    Required Feature: ES47 or GS1280 Series systems
    Superseded Kits: VMS731_EV7-V0200
    Mandatory Kit Dependencies: VMS731_PCSI-V0100
    Optional Kit Dependencies: None


    
    =======================================================================
     Hewlett-Packard OpenVMS ECO Cover Letter
    =======================================================================

             ECO NUMBER:     VMS731_EV7-V0300
             PRODUCT:        OpenVMS Alpha OPERATING SYSTEM V7.3-1
             UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1



1  KIT NAME:

     VMS731_EV7-V0300


2  KIT DESCRIPTION:

     2.1  Installation Rating:


     INSTALL_2: To be installed by all customers using the
                following feature(s):

      -  ES47 or GS1280 Series systems


     This installation rating, based upon current CLD information, is
     provided to serve as a guide to which customers should apply this
     remedial kit.  (Reference attached Disclaimer of Warranty and
     Limitation of Liability Statement)


     2.2  Reboot Requirement:

     Reboot Required.  HP strongly recommends that a reboot is performed
     immediately after kit installation to avoid system instability.

     If you have other nodes in your OpenVMS cluster, they must also  be
     rebooted  in  order  to make use of the new image(s).  If it is not
     possible or convenient to reboot the entire cluster at this time, a
     rolling re-boot may be performed.



     2.3  Version(s) of OpenVMS to which this kit may be applied:

     OpenVMS Alpha V7.3-1


     2.4  New functionality or new hardware support provided:

     No.


3  KITS SUPERSEDED BY THIS KIT:


      -  VMS731_EV7-V0200


                                                                Page 2


4  KIT DEPENDENCIES:

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


      -  VMS731_PCSI-V0100



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


      -  None



5  FILES PATCHED OR REPLACED:


      o  [SYSEXE]APB.EXE (new image)
          
         Image Identification Information
          
         image name: "APB"
         image file identification:  "X-8"
         image file build identification:  "X9EC-0060030002"
         link date/time:  4-NOV-2002 08:53:17.81
         linker identification:  "A11-50"

      o  [SYSLIB]CLUE$SDA.EXE (new image)
          
         Image Identification Information
          
         image name: "CLUE$SDA"
         image file identification:  "X-29"
         image file build identification:  "X9EC-0060030000"
         link date/time: 10-SEP-2002 15:26:02.01
         linker identification:  "A11-50"

      o  [SYSEXE]DCL.EXE (new image)
          
         Image Identification Information
          
         image name: "DCL"
         image file identification:  "X-21A1"
         image file build identification:  "X9EC-0060030004"
         link date/time: 11-NOV-2002 11:46:48.44
         linker identification:  "A11-50"

      o  [SYSEXE]DEBUG_APB.EXE (new image)
          
         Image Identification Information
          
         image name: "DEBUG_APB"

                                                                Page 3


         image file identification:  "X-8"
         image file build identification:  "X9EC-0060030002"
         link date/time:  4-NOV-2002 08:53:18.67
         linker identification:  "A11-50"

      o  [SYSLIB]FC$SDA.EXE (new image)
          
         Image Identification Information
          
         image name: "FC$SDA"
         image file identification:  "X-17"
         image file build identification:  "X9EC-0060030012"
         link date/time: 13-NOV-2002 10:01:41.99
         linker identification:  "A11-50"

      o  [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image)
          
         Image Identification Information
          
         image name: "IMAGE_MANAGEMENT"
         image file identification:  "X-8A1"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:11:55.66
         linker identification:  "A11-50"

      o  [SYS$LDR]IO_ROUTINES.EXE (new image)
          
         Image Identification Information
          
         image name: "IO_ROUTINES"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:11:57.52
         linker identification:  "A11-50"

      o  [SYS$LDR]IO_ROUTINES_MON.EXE (new image)
          
         Image Identification Information
          
         image name: "IO_ROUTINES_MON"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:12:00.20
         linker identification:  "A11-50"

      o  [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image)
          
         Image Identification Information
          
         image name: "PROCESS_MANAGEMENT"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:11:41.58
         linker identification:  "A11-50"

                                                                Page 4


      o  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image)
          
         Image Identification Information
          
         image name: "PROCESS_MANAGEMENT_MON"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:11:52.42
         linker identification:  "A11-50"

      o  [SYS$LDR]RMS.EXE (new image)
          
         Image Identification Information
          
         image name: "RMS"
         image file identification:  "V1.0"
         image file build identification:  "X9EC-0060030001"
         link date/time:  3-SEP-2002 08:46:41.54
         linker identification:  "A11-50"

      o  [SYSLIB]SDARMS$SHARE.EXE (new image)
          
         Image Identification Information
          
         image name: "SDARMS$SHARE"
         image file identification:  "X-9"
         image file build identification:  "X9EC-0060030001"
         link date/time:  3-SEP-2002 08:46:44.94
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$CPU_ROUTINES_270F.EXE (new image)

         Image Identification Information

         image name: "SYS$CPU_ROUTINES_270F"
         image file identification:  "X-1"
         image file build identification: "X9EC-0060030005" 
         link date/time: 20-NOV-2002 15:11:40.36
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$DKDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$DKDRIVER"
         image file identification:  "X-5A1"
         image file build identification:  "X9EC-0060030012"
         link date/time: 13-NOV-2002 10:01:29.41
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$DQDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$DQDRIVER"
         image file identification:  "X-35A1"
         image file build identification:  "X9EC-0060030003"

                                                                Page 5


         link date/time:  6-NOV-2002 08:38:58.83
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$EIDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$EIDRIVER"
         image file identification:  "X-25"
         image file build identification:  "X9EC-0060030000"
         link date/time: 12-AUG-2002 20:14:19.93
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$FGEDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$FGEDRIVER"
         image file identification:  "X-70A3"
         image file build identification:  "X9EC-0060030012"
         link date/time: 13-NOV-2002 10:01:39.26
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$FWBTDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$FWBTDRIVER"
         image file identification:  "X-7"
         image file build identification:  "X9EC-0060030002"
         link date/time:  4-NOV-2002 08:53:18.83
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$GFDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$GFDRIVER"
         image file identification:  "DW V7.3-021016"
         image file build identification:  "X9EC-0060030001"
         link date/time: 16-OCT-2002 09:41:54.26
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$GKDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$GKDRIVER"
         image file identification:  "X-48A1"
         image file build identification:  "X9EC-0060030012"
         link date/time: 13-NOV-2002 10:01:30.84
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$HIDDRIVER.EXE (new image)

         Image Identification Information


                                                                Page 6


         image name: "SYS$HIDDRIVER"
         image file identification: "X-7" 
         image file build identification:"X9EC-0060030006"  
         link date/time: 18-NOV-2002 19:56:18.65
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$HUBDRIVER.EXE (new image)

         Image Identification Information

         image name: "SYS$HUBDRIVER"
         image file identification: "X-7" 
         image file build identification: "X9EC-0060030006"  
         link date/time: 18-NOV-2002 19:56:36.09
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$IKUDRIVER.EXE (new image)

         Image Identification Information

         image name: "SYS$IKUDRIVER"
         image file identification:  "DW V7.3-021111"
         image file build identification:  "X9EC-0060030002"
         link date/time: 11-NOV-2002 10:11:56.91
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$KBDDRIVER.EXE (new image)

         Image Identification Information

         image name: "SYS$KBDDRIVER"
         image file identification: "X-6" 
         image file build identification: "X9EC-0060030006"  
         link date/time: 18-NOV-2002 19:57:05.09
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$LPDRIVER.EXE (new image)

         Image Identification Information

         image name: "SYS$LPDRIVER"
         image file identification: "X-3"  
         image file build identification: "X9EC-0060030006"  
         link date/time: 18-NOV-2002 19:57:24.99
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$MKDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$MKDRIVER"
         image file identification:  "X-12"
         image file build identification:  "X9EC-0060030012"
         link date/time: 13-NOV-2002 10:01:30.26
         linker identification:  "A11-50"

                                                                Page 7


      o  [SYS$LDR]SYS$MOUDRIVER.EXE (new image)

         Image Identification Information

         image name: "SYS$MOUDRIVER"
         image file identification:  "X-2A5"
         image file build identification:  "X9EC-0060030006"
         link date/time: 18-NOV-2002 19:57:13.31
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$OHCIDRIVER.EXE (new image)

         Image Identification Information

         image name: SYS$OHCIDRIVER.EXE
         image file identification:  "X-5"
         image file build identification: "X9EC-0060030006" 
         link date/time: 18-NOV-2002 19:57:19.56
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$PGADRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$PGADRIVER"
         image file identification:  "X-56"
         image file build identification:  "X9EC-0060030012"
         link date/time: 13-NOV-2002 10:01:38.48
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$PKADRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$PKADRIVER"
         image file identification:  "X-25"
         image file build identification:  "X9EC-0060030012"
         link date/time: 13-NOV-2002 10:01:37.43
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$PKQDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$PKQDRIVER"
         image file identification:  "X-21"
         image file build identification:  "X9EC-0060030012"
         link date/time: 13-NOV-2002 10:01:35.17
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$PKRDRIVER.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$PKRDRIVER"
         image file identification:  "X-9"
         image file build identification:  "X9EC-0060030012"

                                                                Page 8


         link date/time: 13-NOV-2002 10:01:35.90
         linker identification:  "A11-50"

      o  [SYSEXE]SYS$SMHANDLER_SLAVE_270F.EXE (new image)

         Image Identification Information

         image name: "SYS$SMHANDLER_SLAVE_270F"
         image file identification:  "X-1"
         image file build identification: "0060030005"
         link date/time: 20-NOV-2002 15:11:39.16
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$USBDRIVER.EXE (new image)

         Image Identification Information

         image name: SYS$USBDRIVER
         image file identification: "X-2"  
         image file build identification: "X9EC-0060030006"  
         link date/time: 18-NOV-2002 19:56:58.24
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$VM.EXE (new image)
          
         Image Identification Information
          
         image name: "SYS$VM"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:12:03.74
         linker identification:  "A11-50"

      o  [SYS$LDR]SYS$YCDRIVER.EXE (new image)

         Image Identification Information

         image name: SYS$YCDRIVER
         image file identification: "X-6"  
         image file build identification: "X9EC-0060030006"  
         link date/time: 18-NOV-2002 19:57:37.14
         linker identification:  "A11-50"

      o  [SYS$LDR]SYSDEVICE.EXE (new image)
          
         Image Identification Information
          
         image name: "SYSDEVICE"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:12:08.13
         linker identification:  "A11-50"

      o  [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image)
          
         Image Identification Information
          

                                                                Page 9


         image name: "SYSTEM_PRIMITIVES"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:11:55.82
         linker identification:  "A11-50"

      o  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image)
          
         Image Identification Information
          
         image name: "SYSTEM_PRIMITIVES_MIN"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:11:53.24
         linker identification:  "A11-50"

      o  [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE (new image)
          
         Image Identification Information
          
         image name: "SYSTEM_SYNCHRONIZATION"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:12:02.35
         linker identification:  "A11-50"

      o  [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE (new image)
          
         Image Identification Information
          
         image name: "SYSTEM_SYNCHRONIZATION_MIN"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:12:03.31
         linker identification:  "A11-50"

      o  [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE (new image)
          
         Image Identification Information
          
         image name: "SYSTEM_SYNCHRONIZATION_UNI"
         image file identification:  "X-3"
         image file build identification:  "X9EC-0060030017"
         link date/time: 20-NOV-2002 15:12:05.14
         linker identification:  "A11-50"

      o  [SYSMSG]USB$MSG.EXE (new image)

         Image Identification Information

         image name: "USB$MSG"
         image file identification:  "X-7"
         image file build identification:  "X9EC-0060030000"
         link date/time: 18-NOV-2002 19:57:27.94
         linker identification:  "A11-50"

                                                               Page 10


      o  [SYSEXE]USB$UCM_SERVER.EXE (new image)

         Image Identification Information

         image name: "USB$UCM_SERVER"
         image file identification:  "X-10"
         image file build identification:  "0060030006"
         link date/time: 18-NOV-2002 19:57:45.12
         linker identification:  "A11-50"

      o  [SYSEXE]APB_BOOTP.EXE (new image)

      o  [SYSUPD]DCLINT.CLD (new file)

      o  [SYS$LDR]IMAGE_MANAGEMENT.STB (new file)

      o  [SYS$LDR]IO_ROUTINES.STB (new file)

      o  [SYS$LDR]IO_ROUTINES_MON.STB (new file)

      o  [SYS$LDR]PROCESS_MANAGEMENT.STB (new file)

      o  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file)

      o  [SYSLIB]RMSDEF.STB (new file)

      o  [SYS$LDR]SYS$CONFIG.DAT (new file)

      o  [SYS$LDR]SYS$VM.STB (new file)

      o  [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file)

      o  [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file)

      o  [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB (new file)

      o  [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB (new file)

      o  [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB (new file)

      o  [SYSMGR]USB$STARTUP.COM (new file)

      o  [SYS$STARTUP]VMS$CONFIG-050_LMF.COM (new file)

      o  [SYS$STARTUP]VMS$DEVICE_STARTUP.COM (new file)



6  PROBLEMS ADDRESSED IN THIS KIT


                                                               Page 11


     6.1  New problems addressed in the VMS731_EV7-V0300 kit

          6.1.1  Bootblock      Corruption      after      un-installing
                 VMS731_EV7-V0200 ECO kit

               6.1.1.1  Problem Description:

               If the VMS731_EV7-V0200 ECO kit is removed using PRODUCT
               UNDO PATCH, the boot block locaton is invalid after the
               UNDO completes.  This may prevent a system from rebooting
               if the origial bootblock gets overwritten with other
               data.

               Images Affected:

                -  [SYSUPD]POSTUNDO.COM



               6.1.1.2  CLDs, and QARs reporting this problem:

                    6.1.1.3  CLD(s)

                    70-3-7378


                    6.1.1.4  QAR(s)

                    None.


               6.1.1.5  Problem Analysis:

               The POSTUNDO.COM installation procedure performs a
               writeboot when a kit is un-installed using the PCSI UNDO
               PATCH feature.  This procedure was being executed before
               all file processing had completed.


               6.1.1.6  Work-arounds:

               If you have already installed the VMS731_EV7-V0200 ECO
               kit there is no need to install the VMS731_EV7-V0300 kit.
               To correct the boot problems on the boot disk, execute an
               MC WRITEBOOT command from a privileged account and answer
               the prompts as shown:

               $ MC WRITEBOOT
               Update VAX portion of boot block (default is Y) : N
               Update AXP portion of boot block (default is Y) : Y
               Enter AXP boot file :SYS$COMMON:[SYSEXE]APB.EXE
               $


                                                               Page 12


7  INSTALLATION INSTRUCTIONS:

     7.1  Installation Command

     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 VMS731_EV7 /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



     7.2  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

      -  $ DEFINE/SYS NO_ASK$REBOOT TRUE

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

           /PROD=DEC/BASE=AXPVMS/VER=V3.0


      -  De-assign the logicals assigned

     For example, a sample command file to install the VMS731_EV7-V0300
     kit would be:

     $
     $ DEFINE/SYS NO_ASK$BACKUP TRUE
     $ DEFINE/SYS NO_ASK$REBOOT TRUE
     $!
     $ PROD INSTALL VMS731_EV7/PROD=DEC/BASE=AXPVMS/VER=V3.0
     $!
     $ DEASSIGN/SYS NO_ASK$BACKUP
     $ DEASSIGN/SYS NO_ASK$REBOOT
     $!
     $ exit


                                                               Page 13


     7.3  Special Installation Instructions:

     If you have already installed the VMS731_EV7-V0200 ECO kit there is
     no  need  to install the VMS731_EV7-V0300 kit.  To correct the boot
     problems on the boot disk, execute an MC WRITEBOOT command  from  a
     privileged account and answer the prompts as shown:

     $ MC WRITEBOOT
     Update VAX portion of boot block (default is Y) : N
     Update AXP portion of boot block (default is Y) : Y
     Enter AXP boot file :SYS$COMMON:[SYSEXE]APB.EXE
     $



8  COPYRIGHT AND DISCLAIMER:

     (C) Copyright 2003 Hewlett-Packard Development Company, L.P.

     Confidential computer software.  Valid license from HP  and/or  its
     subsidiaries required for possession, use, or copying.

     Consistent  with  FAR  12.211  and  12.212,   Commercial   Computer
     Software,  Computer  Software Documentation, and Technical Data for
     Commercial  Items  are  licensed  to  the  U.S.   Government  under
     vendor's standard commercial license.

     Neither HP  nor  any  of  its  subsidiaries  shall  be  liable  for
     technical  or  editorial errors or omissions contained herein.  The
     information in this document is provided "as is"  without  warranty
     of  any  kind  and  is  subject  to  change  without  notice.   The
     warranties for HP products are set forth  in  the  express  limited
     warranty  statements  accompanying  such  products.  Nothing herein
     should be construed as constituting an additional warranty.

     DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY

     THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF  ANY  KIND.   ALL
     EXPRESS  OR  IMPLIED  CONDITIONS,  REPRESENTATIONS  AND WARRANTIES,
     INCLUDING ANY IMPLIED  WARRANTY  OF  MERCHANTABILITY,  FITNESS  FOR
     PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE
     EXTENT PERMITTED BY APPLICABLE LAW.  IN NO  EVENT  WILL  COMPAQ  BE
     LIABLE  FOR  ANY  LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT,
     CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER  CAUSED  AND
     REGARDLESS  OF  THE  THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH
     MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.