ECO NUMBER:     VAXSCSI01_062
             PRODUCT:        OpenVMS VAX OPERATING SYSTEM 6.2
             UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2




                                COVER LETTER


1  KIT NAME:

     VAXSCSI01_062


2  KITS SUPERSEDED BY THIS KIT:

     None


3  KIT DESCRIPTION:

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

     OpenVMS VAX V6.2


     3.2  In order to receive the full fixes  listed  in  this  kit  the
          following remedial kits also need to be installed:

     None


     3.3  Files patched or replaced:


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

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

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

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

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

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

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



4  PROBLEMS ADDRESSED IN VAXSCSI01_062 KIT


      o  System bugchecks with ACCVIO.  The PC of the crash  is  usually
         in the middle of a structure, or some other nonsense address.

      o  MOUNT/CLUSTER/NOWRITE does not write lock on the node which own
         the disk

-- COVER LETTER --                                              Page 2
                                                       9 December 1997


      o  Devices that implement AEN  (Asynchronous  Event  Notification)
         may exhibit problems when used on a VaxStation 4000.

      o  Sending an illegal IO$_AUDIO function to DKDRIVER can result in
         a system crash, from user mode and without privilege.

      o  VAXstation 4000-90s, VAXserver 3100-90s and later will not boot
         if system disk is in a HSZ10.

         This problem is corrected in OpenVMS VAX V7.1.

      o  An  INVEXCEPTN  bugcheck  can  occur  in  DEQUE_DEV_IO   if   a
         disconnected  command times out while a Request Sense is taking
         place.

      o  Under  certain  circumstances,  targets  can  go   into   mount
         verification without any error being logged into the errorlog.

      o  If a WFIKPCH  times  out,  instruction  stream  code  bits  are
         modified.  Later, attempts to execute this modified instruction
         stream causes system crashes and other problems.

      o  SCSI bus errors can cause OpenVMS to crash with  an  SPLIPLHIGH
         bugcheck.  This problem is corrected in OpenVMS Alpha V7.1.

      o  Problems have been reported both with third  party  archiever's
         that  place  data  after  the  initial  EOT  on a tape and with
         Desktop Backup when using the "fast skipfile"  behavior.   This
         update,  returns  to  the  old  skip file by records algorithm.
         However, users who want to have the ~60 fold  speedup  in  tape
         positioning can use a new utility to enable it.

         This problem is corrected in OpenVMS VAX V7.1

      o  Many errors are logged where in effect a single SCSI reset  has
         occurred.  This problem is corrected in OpenVMS VAX V7.1

      o  When a tagged command times out and  the  port  has  a  request
         sense  in  progress to the device, the appearance of the tagged
         queue when only tag 0 is expected causes a INCONSTATE bugcheck.

         This problem is corrected in OpenVMS VAX V7.1



5  KIT INSTALLATION RATING:

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

     INSTALLATION RATING:

       INSTALL_1 : To be installed by all customers.


-- COVER LETTER --                                              Page 3
                                                       9 December 1997


6  INSTALLATION INSTRUCTIONS:

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

         @SYS$UPDATE:VMSINSTAL VAXSCSI01_062 [location of the saveset]

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

     System should be rebooted after successful installation of the kit.
     If  you  have  other  nodes in your VMScluster, they should also be
     rebooted in order to make use of the new image(s).


     Copyright  (c)  Digital  Equipment  Corporation,  1997  All  Rights
     Reserved.   Unpublished rights reserved under the copyright laws of
     the United States.

     The software contained on this media is proprietary to and embodies
     the  confidential  technology  of  Digital  Equipment  Corporation.
     Possession, use, or dissemination of  the  software  and  media  is
     authorized  only  pursuant  to a valid written license from Digital
     Equipment Corporation.

     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  DIGITAL  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.