=======================================================================
     Hewlett-Packard OpenVMS ECO Release Notes
    =======================================================================







1  KIT NAME:

     VMS84I_UPDATE-V0300



2  KIT DESCRIPTION:

     2.1  Installation Rating:

     INSTALL_1 :  To be installed by all customers for 
     HP Integrity server blades and HP Integrity server systems. 
     HP's support service is available only if INSTALL_1 is applied.



     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
     reboot may be performed.



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

     OpenVMS for Integrity servers V8.4



     2.4  New functionality or new hardware support provided:

     Yes. See the following file for more information:
 
      o  [SYSHLP]VMS84I_UPDATE-V0200
 
 

3  KITS SUPERSEDED BY THIS KIT:



      -  VMS84I_UPDATE-V0200





4  KIT DEPENDENCIES:

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



      -  None



     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  NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE
   VMS84I_UPDATE-V0300 KIT

     5.1  New functionality addressed in this kit

             5.1.1 Tape Blade support on BL8x0c i2 server blades

               VMS84I_UPDATE-V0300 kit supports tape blades on
               BL8x0c i2 server blades. The following tape blades 
               are supported: 
               - HP StorageWorks SB1760c Tape Blade
               - HP StorageWorks SB920c Tape Blade
               - HP StorageWorks Ultrium 448c Tape Blade
               
               For technical specifications and additional
               configuration information, see the QuickSpecs at: 
 
               http://h18000.www1.hp.com/products/quickspecs/12729_div/12729_div.PDF



             5.1.2  Broadcom 57711E support
           
               It is mandatory to install the VMS84I_UPDATE-V0300 
               update kit to support the Broadcom 57711E based 
               dual-port LAN device (LOM or NC532m mezzanine card or 
               others). 



     5.2  Problems addressed in this kit

        
               5.2.1  Setting SCH_HARD_OFFLD to non-zero on an 
                      Integrity cell-based system with RAD support 
                      enabled may crash the system

                    5.2.1.1  Problem Description:

                    On an Integrity cell-based system with RAD support 
                    enabled, if you also have the SYSGEN parameter, 
                    SCH_HARD_OFFLD set to non-zero, OpenVMS system may 
                    crash occasionally with the CPUSPINWAIT bugcheck code.

                    This problem has been fixed.



                    Images Affected:

                     -  PROCESS_MANAGEMENT.EXE

                     -  PROCESS_MANAGEMENT_MON.EXE
             
                     -  PROCESS_MANAGEMENT.STB

                     -  PROCESS_MANAGEMENT_MON.STB



                    5.2.1.2  Work-arounds:

                    None.



      
               5.2.2  ERRORLOG.SYS not available for 20-40 minutes after 
                      boot time

                    5.2.2.1  Problem Description:

                    On BL870c i2 and BL890c i2 server blades, the ERRORLOG.SYS 
                    file is not available for 20-40 minutes after boot time. 
                    Because of this delay you cannot analyze the logs for 
                    this time period. This delay is caused from gathering 
                    the configuration information on a multi-blade system, 
                    which is a slow process. 
    
                    This problem has been fixed.



                    Images Affected:

                     -  ERRFMT.EXE



                    5.2.2.2 Work-arounds:

                    None.

 
6   KNOWN PROBLEMS AND LIMITATIONS

      This section describes the known problems and limitations
      in this patch kit.



      o  HP VMS SSL V1.4 provided with OpenVMS V8.4 for Integrity
         servers and Alpha systems is not backward compatible

      Applications built with HP VMS SSL V1.3 (based on OpenSSL 0.9.7e) 
      will not work with HP VMS SSL V1.4 (based on OpenSSL 0.9.8h). 

      Some of the OpenSSL APIs, data structures, and commands 
      have changed from the OpenSSL version 0.9.7e to OpenSSL 
      version 0.9.8h, thus resulting in backward compatibility  
      issues. Applications have to be recompiled and rebuilt with  
      the SSL V1.4 header files and libraries to work correctly.

      For more information, see the HP SSL for OpenVMS website: 
      http://h71000.www7.hp.com/openvms/products/ssl/ssl.html



      o  Discrepancies in NPAGERAD and NPAGEDYN values on Integrity
         servers and Integrity blades with RAD support



      When support for RAD (Resource Affinity Domain) and per-RAD 
      non-paged pool are enabled on Integrity cell-based systems 
      and BL8x0c i2 server blades, the distribution of non-paged 
      pool over the base RAD and the remaining RADs does not comply 
      with the documentation mentioned under NPAGERAD in HP OpenVMS 
      System Management Utilities Reference Manual: M-Z for V8.4.

      NOTE: The value of 10944731 in the RAD_SUPPORT parameter 
      enables support for RAD and per-RAD non-paged pool.

      As mentioned in the guide:

      - By default, when NPAGERAD is 0, the system must compute 
      NPAGERAD using the following formula:

      NPAGERAD= NPAGEDYN * (1- Base RAD memory/ Total memory)

      Currently, the system does not calculate the value required 
      for NPAGERAD. The NPAGERAD value remains as 0 and per-RAD 
      non-paged pool is not enabled.

      - When NPAGERAD is non-zero, the system must distribute 
      the non-paged pool over the base RAD and the remaining RADs
      such that NPAGEDYN corresponds to the total amount of non-paged 
      pool in the system. The NPAGERAD corresponds to the amount of 
      non-paged pool from the RADs other than the base RAD. 
      For example, if the system is configured with:
 
      NPAGEDYN = 6291456 bytes and
      NPAGERAD = 2097152 bytes,

      OpenVMS must allocate a total of approximately 6,291,456 bytes 
      of non-paged pool. Of this amount, the system must divide 
      2,097,152 bytes among the RADs that are not the base RAD. 

      However, OpenVMS divides 2,097,152 bytes among the RADs that 
      are not the base RAD and assigns 6,291,456 bytes to the base RAD. 
      Hence, in this scenario the system has a total of 
      8,388,608 (NPAGEDYN+NPAGERAD) bytes.

      These discrepancies will be addressed in a future update kit.



      o  Broadcom 57711E LAN device requires more non-paged pool

      The Broadcom 57711E based dual-port LAN device (LOM or NC532m 
      mezzanine card or other) requires additional non-paged pool. 
      For each 57711E based dual-port LOM/card, HP recommends 
      increasing the SYSGEN parameter, NPAGEDYN by 26800000.
                         
      To increase NPAGEDYN, add the ADD_NPAGEDYN parameter to
      MODPARAMS.DAT and run AUTOGEN. For example, add the
      following command to MODPARAMS.DAT on a system with two
      57711E LOM:
 
      ADD_NPAGEDYN = 53600000

 
      o  Issue with OpenVMS on BL890c i2 server blade with all 
         the 96 memory slots populated with 4 GB memory DIMMs

      On a BL890c i2 server blade with all the 96 memory slots 
      populated with 4 GB dual in-line memory module (DIMMs) 
      (96 * 4 GB = 384 GB) and with the system memory interleaved 
      configuration being MostlyNUMA or Balanced, the system 
      becomes unstable resulting in a crash.

      In this scenario, HP recommends you to change the system 
      memory interleaved configuration to one of the following 
      options available on OpenVMS systems:
      - MaxNUMA
      - MostlyUMA
      - MaxUMA

      This can be done at the EFI shell by invoking the 
      "memconfig -mi <option>" command with one of these options. 
      The server needs to be reset for this change to take effect.

      Most of the problems related to this issue have been fixed 
      in this update. OpenVMS Engineering continues to test this 
      configuration and the restriction will be removed in a future 
      update.



7  KNOWN PROBLEMS AND LIMITATIONS IN PREVIOUS KITS

     Known problems and limitations in the previously released 
     VMS84I_UPDATE patch kits can be found in the following files:

      o  VMS84I_UPDATE-V0200.RELEASE_NOTES

     Before kit installation, these files can be extracted from the kit
     via the following commands:

      o  To extract all release notes files at once use:

         PRODUCT EXTRACT RELEASE_NOTES VMS84I_UPDATE /VERSION=V3.0 -
         [/file=destination_directory]

      o  To extract a single release notes file use:

         PRODUCT EXTRACT FILE VMS84I_UPDATE /VERSION=V3.0 -
         /SELECT=release_note_name[/DESTINATION=destination_directory]

         The names of individual RELEASE_NOTES files in the kit can be
         found with:

         PRODUCT LIST VMS84I_UPDATE /VERSION=V3.0 /SELECT = *.RELEASE_NOTES





8  FILES PATCHED OR REPLACED:



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

         Image Identification Information
         image name: "SYS$EW57711DRIVER_MON"
         image file identification: "X-5"
         image file build identification: "0100000001"
         link date/time: 20-JUL-2010 18:26:25.36
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 9D59FB31

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

         Image Identification Information

         image name: "SYS$EW57711DRIVER"
         image file identification: "X-5"
         image file build identification: "0100000001"
         link date/time: 20-JUL-2010 18:26:22.64
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 29B5E361

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

         Image Identification Information

         image name: "SYS$EW57711DRIVER_MON"
         image file identification: "X-5"
         image file build identification: "0100000001"
         link date/time: 20-JUL-2010 18:26:25.36
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 9D59FB31

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

         Image Identification Information

         image name: "SYS$EW57711DRIVER"
         image file identification: "X-5"
         image file build identification: "0100000001"
         link date/time: 20-JUL-2010 18:26:22.64
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 29B5E361

      o  [SYSLIB]SPL$SDA.EXE (new image)

         Image Identification Information

         image name: "SPL$SDA"
         image file identification: "X-43"
         image file build identification: "XC9U-BL1-000000"
         link date/time: 14-MAY-2010 23:11:24.22
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 1E5B7D4B

      o  [SYSLIB]PRF$SDA.EXE (new image)

         Image Identification Information

         image name: "PRF$SDA"
         image file identification: "X-27"
         image file build identification: "XC9U-BL1-000000"
         link date/time: 14-MAY-2010 23:12:03.64
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 5A37FC1

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

         Image Identification Information

         image name: "PRF$DEBUG"
         image file identification: "X-5"
         image file build identification: "XC9U-BL1-000000"
         link date/time: 14-MAY-2010 23:12:00.06
         linker identification:  "Linker I02-37"
         Overall Image Checksum: ED13E52B

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

         Image Identification Information

         Image name: "SYS$GSPDRIVER"
         image file identification:  "X-5"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:11:58.96
         Overall Image Checksum: 178D3280

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

         Image Identification Information

         Image name: "SYS$GSPBTDRIVER"
         image file identification:  "X-5"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:11:52.36
         Overall Image Checksum: 85D507F2

      o  [SYSLIB]CLUE$SDA.EXE (new image)

         Image Identification Information

         Image name: "CLUE$SDA"
         image file identification:  "X-67"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:09:24.53
         Overall Image Checksum: C2761DE8

      o  [SYSEXE]DCL.EXE (new image)

         Image Identification Information

         Image name: "DCL"
         image file identification:  "X-54"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:09:30.54
         Overall Image Checksum: 8069E48A

      o  [SYSEXE]EFI$BCFG.EXE (new image)

         Image Identification Information

         Image name: "EFI$BCFG"
         image file identification:  "X-39"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:09:55.67
         Overall Image Checksum: 1001028A

      o  [SYSEXE]ERRFMT.EXE (new image)

         Image Identification Information

         Image name: "ERRFMT"
         image file identification:  "X-22"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 10-JUL-2010 11:06:08.54
         Overall Image Checksum: 3DC5D7DA

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

         Image Identification Information

         Image name: "EXEC_INIT"
         image file identification:  "X-217"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 29-JUL-2010 16:51:07.15
         Overall Image Checksum: 2843D640

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

         Image Identification Information

         Image name: "SYSLDR_DYN"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 29-JUL-2010 16:51:30.37
         Overall Image Checksum: A4D8AAE5

      o  [SYSLIB]IOGEN$ISA_CONFIG.EXE (new image)

         Image Identification Information

         Image name: "IOGEN$ISA_CONFIG"
         image file identification:  "X-21"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:07:19.51
         Overall Image Checksum:  A82BC75

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

         Image Identification Information

         Image name: "RMS"
         image file identification:  "X-5"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:11:02.26
         Overall Image Checksum: 4720D9D0

      o  [SYSLIB]SDA$SHARE.EXE (new image)

         Image Identification Information

         Image name: "SDA$SHARE"
         image file identification:  "X-2"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:11:20.83
         Overall Image Checksum:  A55DD44

      o  [SYSEXE]SMPUTIL.EXE (new image)

         Image Identification Information

         Image name: "SMPUTIL"
         image file identification:  "X-30"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:10:06.48
         Overall Image Checksum:  4ECACE4

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

         Image Identification Information

         Image name: "SYS$BASE_IMAGE"
         image file identification:  "IA64 XC9U-J2I"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:04:23.07
         Overall Image Checksum: 6B2BF385

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

         Image Identification Information

         Image name: "SYS$CMDRIVER"
         image file identification:  "X-5"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:09:58.71
         Overall Image Checksum: BDD7DC5C

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

         Image Identification Information

         Image name: "SYS$GHDRIVER"
         image file identification:  "DW V8.4-100514"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 15-MAY-2010 00:24:57.09
         Overall Image Checksum: 9F58F09B

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

         Image Identification Information

         Image name: "SYS$HWP0001"
         image file identification:  "X-35"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:10:27.37
         Overall Image Checksum:  3083FF7

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

         Image Identification Information

         Image name: "SYS$HWP0004"
         image file identification:  "X-35"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:10:30.81
         Overall Image Checksum: BEFFC254

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

         Image Identification Information

         Image name: "SYS$PCIE_SUPPORT"
         image file identification:  "X-35"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:10:53.70
         Overall Image Checksum: BFFB6434

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

         Image Identification Information

         Image name: "SYS$PCI_SUPPORT"
         image file identification:  "X-35"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:10:20.78
         Overall Image Checksum: DF096D31

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

         Image Identification Information

         Image name: "SYS$PLATFORM_SUPPORT"
         image file identification:  "X-35"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:10:17.27
         Overall Image Checksum: D8E4B167

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

         Image Identification Information

         Image name: "SYS$SRDRIVER"
         image file identification:  "X-5"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:10:53.93
         Overall Image Checksum: 80BEC6FA

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

         Image Identification Information

         Image name: "SYS$TRANSACTION_SERVICES"
         image file identification:  "V2.1-X035-XC9U"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:09:45.51
         Overall Image Checksum: 277B1C09

      o  [SYSEXE]SYSINIT.EXE (new image)

         Image Identification Information

         Image name: "SYSINIT"
         image file identification:  "X-124"
         image file build identification:  "XC9U-BL1-000000"
         linker identification:  "Linker I02-37"
         Link Date/Time: 14-MAY-2010 23:11:15.33
         Overall Image Checksum: FD907C7E

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

         Image Identification Information

         Image name: "SYSTEM_PRIMITIVES"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:47.00
         Overall Image Checksum: 15B99566

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

         Image Identification Information

         Image name: "SYSTEM_PRIMITIVES_MIN"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:52.67
         Overall Image Checksum: E61F517A

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

         Image Identification Information

         Image name: "SYSTEM_SYNCHRONIZATION"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:01:59.90
         Overall Image Checksum: BB2D9D4D

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

         Image Identification Information

         Image name: "SYSTEM_SYNCHRONIZATION_MIN"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:01:58.78
         Overall Image Checksum: 93232496

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

         Image Identification Information

         Image name: "SYSTEM_SYNCHRONIZATION_UNI"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:01.28
         Overall Image Checksum: 6E4B1137

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

         Image Identification Information

         image name: "SYS$PEDRIVER"
         image file identification: "X-5"
         image file build identification: "XC9U-BL1-000000"
         link date/time: 14-MAY-2010 23:09:13.45
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 92250D46

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

         Image Identification Information

         image name: "SYS$PEDRIVER_MON"
         image file identification: "X-5"
         image file build identification: "XC9U-BL1-000000"
         link date/time: 14-MAY-2010 23:09:19.20
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 664B72BC

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

         Image Identification Information

         image name: "SYS$CLUSTER"
         image file identification: "X-5"
         image file build identification: "XC9U-BL1-000000"
         link date/time: 14-MAY-2010 23:10:31.02
         linker identification:  "Linker I02-37"
         Overall Image Checksum: F224E16E

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

         Image Identification Information

         image name: "SYS$CLUSTER_MON"
         image file identification: "X-5"
         image file build identification: "XC9U-BL1-000000"
         link date/time: 14-MAY-2010 23:10:35.02
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 9D8ABBC6

      o  [SYSLIB]DECC$SHR.EXE (new image)

         Image Identification Information

         image name: "DECC$SHR"
         image file identification: "V8.4-00"
         image file build identification: "XC9Y-BL1-000000"
         link date/time: 8-JUN-2010 13:30:42.06
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 7FE1FD33

      o  [SYSLIB]DECC$SHRP.EXE (new image)

         Image Identification Information

         image name: "DECC$SHRP"
         image file identification: "V8.4-00"
         image file build identification: "XC9Y-BL1-000000"
         link date/time: 8-JUN-2010 13:30:37.08
         linker identification:  "Linker I02-37"
         Overall Image Checksum: 4D117F3A

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

         Image Identification Information

         image name: "SYS$PKRDRIVER"
         image file identification: "X-5"
         image file build identification: "XCA2-BL1-000000"
         link date/time: 16-JUN-2010 17:13:41.21
         linker identification:  "Linker I02-37"
         Overall Image Checksum: AA3C0964

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

         Image Identification Information

         Image name: "SYS$VM"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:27.04
         Overall Image Checksum: 970FF4D8

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

         Image Identification Information

         Image name: "IO_ROUTINES"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 29-JUL-2010 16:51:19.87
         Overall Image Checksum: 54ABEDEB

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

         Image Identification Information

         Image name: "IO_ROUTINES_MON"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 29-JUL-2010 16:51:25.77
         Overall Image Checksum: 61933C86

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

         Image Identification Information

         Image name: "SHELL8K"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:14.62
         Overall Image Checksum: F0A253C9

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

         Image Identification Information

         Image name: "SHELL16K"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:17.07
         Overall Image Checksum: 1AE63341

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

         Image Identification Information

         Image name: "SHELL32K"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:19.42
         Overall Image Checksum: 2184E69D

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

         Image Identification Information

         Image name: "SHELL64K"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:21.87
         Overall Image Checksum: 25B24713

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

         Image Identification Information

         Image name: "SYS$LASTDRIVER"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:07.00
         Overall Image Checksum: EE4DD88B

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

         Image Identification Information

         Image name: "SYS$PKMDRIVER"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:02:44.61
         Overall Image Checksum: D05BFF6E

      o  [SYSLIB]PKM$SDA.EXE (new image)

         Image Identification Information

         Image name: "PKM$SDA"
         image file identification:  "X-29"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 6-JUL-2010 19:03:08.50
         Overall Image Checksum: 7C814B0B

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

         Image Identification Information

         Image name: "PROCESS_MANAGEMENT"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 10-JUL-2010 11:07:11.06
         Overall Image Checksum: 48BD7B80

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

         Image Identification Information

         Image name: "PROCESS_MANAGEMENT_MON"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 10-JUL-2010 11:07:18.56
         Overall Image Checksum: 7AB54C80

      o  [SYSEXE]F11CACP.EXE (new image)

         Image Identification Information

         Image name: "F11CACP"
         image file identification:  "X-13"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 10-JUL-2010 11:06:06.24
         Overall Image Checksum: 8B9AA13B

      o  [SYSEXE]F11DACP.EXE (new image)

         Image Identification Information

         Image name: "F11DACP"
         image file identification:  "X-13"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 10-JUL-2010 11:06:10.53
         Overall Image Checksum: 985C242F

      o  [SYSEXE]SYSBOOT.EXE (new image)

         Image Identification Information

         Image name: "SYSBOOT"
         image file identification:  "X-152"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 10-JUL-2010 11:06:26.73
         Overall Image Checksum: 1DC9CC54

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

         Image Identification Information

         Image name: "SYSGETSYI"
         image file identification:  "X-5"
         image file build identification:  "0100000001"
         linker identification:  "Linker I02-37"
         Link Date/Time: 15-JUL-2010 19:16:03.48
         Overall Image Checksum: E2C8DB75

      o  [SYSMGR]CLUSTER_CONFIG.COM (new file)

      o  [SYS$LDR]CLUSTER_CONFIG_LAN.COM (new file)

      o  [SYS$LDR]SYS$LIB_C.TLB (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  [SYS$STARTUP]VMS$DEVICE_STARTUP.COM (new file)

      o  [SYSEXE]VMS_BCFG.EFI (new file)

      o  [SYSEXE]VMS_SET.EFI (new file)

      o  [SYSEXE]VMS_SHOW.EFI (new file)

      o  [SYSMGR]CLUSTER_CONFIG.COM (new file)

      o  [SYS$LDR]CLUSTER_CONFIG_LAN.COM (new file)

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

      o  [SYSEXE]I64VMS$PCSI_INSTALL_MIN.COM (new file)

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

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

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

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

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

      o  [SYSLIB]LIB.MLB (new file)

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

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

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

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

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

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

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

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

      o  [SYSLIB]AUTOGEN.COM (new file)

      o  [SYSLDR]EXEC_INIT.STB (new file)

      o  [SYSLDR]SYSLDR_DYN.STB (new file)





9  INSTALLATION INSTRUCTIONS

     9.1  Test/Debug Image Loss

     In the course of debugging problems reported to OpenVMS
     Engineering, customers may be given debug or point-fix images to
     install.  Typically, these images do not have the same image
     generation flags contained in images released via the OpenVMS
     remedial patch process.  Because of this, any debug or point-fix
     image that is in the SYS$COMMON area, will be replaced by any image
     of the same name installed by this kit.  If this occurs, you will
     lose any functionality that is provided by the replaced image.  If
     you want to retain these debug or point-fix images, you can take
     the following steps:

      o  Prior to installing this kit, move the test/debug image(s) to
         be saved to the SYS$SPECIFIC area.

      o  During kit installation, you will be asked if you want to
         delete the image(s) in SYS$SPECIFIC.  You should answer NO for
         each image that you want to keep.

      o  After installation completes, but before rebooting the system
         (if required), move the image(s) from SYS$SPECIFIC back to
         SYS$COMMON.





     9.2  Compressed File

     This kit is provided as a Self Extracting ZIPEXE kit.  To expand
     this file to the installable .PCSI file, run the file with the
     following command:

     $ RUN VMS84I_UPDATE-V0300.ZIPEXE





     9.3  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 VMS84I_UPDATE[/SOURCE=location of Kit]

     Note that this kit will install with the /SAVE_RECOVERY_DATA option
     turned on.  Using this qualifier will allow easy removal of the kit
     from the system in the event of problems.  If you want to disable
     this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the
     PRODUCT INSTALL command.  The /SAVE_RECOVERY_DATA qualifier is
     optional but highly recommended.  Using this qualifier will allow
     easy removal of the kit from the system in the event of problems.

     The kit location may be a tape drive, CD, or a disk directory that
     contains the kit.  The /SOURCE qualifier is not needed if the
     PRODUCT INSTALL command is executed from the same directory as the
     kit location.

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



     9.4  Scripting of Answers to Installation Questions

     During installation, this kit will ask and require user response to
     several questions.  If you want 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
     logical name definitions and commands:

      o  To avoid the BACKUP question, define the following:

              $ DEFINE/SYS NO_ASK$BACKUP TRUE

      o  To save replaced files as *.*_OLD define the following logical
         name as YES.  If you do not wish to save replaced files, define
         the logical name as NO.  Note that if you use the
         /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT
         INSTALL command all replaced files will be saved as part of
         that operation.  There is no need to also save files as
         *.*_OLD:

            $ DEFINE/JOB ARCHIVE_OLD NO

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

           /PROD=HP/BASE=I64VMS/VER=V3.0 [/SOURCE=location of Kit]



      o  De-assign the logical names assigned



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

     $ DEFINE/SYS NO_ASK$BACKUP TRUE
     $ DEFINE/JOB ARCHIVE_OLD NO
     $!
     $ PROD INSTALL VMS84I_UPDATE/PRODUCER=HP/BASE=I64VMS/VER=V3.0"
     $!
     $ DEASSIGN/SYS NO_ASK$BACKUP
     $!
     $ exit
     $!



10  COPYRIGHT AND DISCLAIMER:

     (C) Copyright 2010 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 HP 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.