OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: system PRIVILEGED account (rootnfsserver.support.compaq.com)
Date: Tue Feb 13 2001 - 03:30:27 CST

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

    *******************************************************************************
    * *
    * This is an update to an existing patch... *
    * *
    * Online links can be found at *
    * http://ftp.support.compaq.com/patches/public/vms/axp/v7.1-2/dec-axpvms-vms712_scsi-v0300--4.README
    *******************************************************************************

    TITLE: OpenVMS VMS712_SCSI-V0300 Alpha V7.1-2 SCSI Drivers ECO Summary

    New Kit Date : 13-FEB-2001
    Modification Date: Not Applicable
    Modification Type: Updated Kit Supersedes VMS712_SCSI-V0200
     
    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 2000. All rights reserved.

    OP/SYS: OpenVMS Alpha V7.1-2

    COMPONENT: SCSI Drivers

    SOURCE: Compaq Computer Corporation

    ECO INFORMATION:

         ECO Kit Name: VMS712_SCSI-V0300
                        DEC-AXPVMS-VMS712_SCSI-V0300--4.PCSI
         ECO Kits Superseded by This ECO Kit: VMS712_SCSI-V0200
         ECO Kit Approximate Size: 2288 Blocks
         Kit Applies To: OpenVMS Alpha V7.1-2
         System/Cluster Reboot Necessary: Yes
         Rolling Re-boot Supported: Yes
         Installation Rating: INSTALL_1
                               To be installed by all customers.

         Kit Dependencies:

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

             VMS712_UPDATE-V0300
             VMS62TO71U2_PCSI-V0200

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

             None

    ECO KIT SUMMARY:

    An ECO kit exists for SCSI on OpenVMS Alpha V7.1-2. This kit addresses
    the following problems:

    PROBLEMS ADDRESSED IN VMS712_SCSI-V0300 KIT

      o The ESL9198DLX tape library was not recognized by VMS when
         booting. In PK$NEGOTIATE_SYNCH, which is called by
         PK$INIT_STDT, the connection parameters were not being
         properly set up.

            Images Affected: [SYS$LDR]SYS$PKWDRIVER.EXE

      o The system can crash if AUTOGEN is run while a tape backup is
         running.

            Images Affected: [SYS$LDR]SYS$PKWDRIVER.EXE

      o A system can crash with an INVEXCEPTN bugcheck during error
         processing.

            Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE

    PROBLEMS ADDRESSED IN VMS712_SCSI-V0200 KIT

      o A disk could be mounted and write protected, then dismounted
         with the write protection cleared. When it is remounted,
         however, the disk may still be write locked.

           Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE

      o Provide support for the Adaptec 7895/7899 SCSI port driver.

           Images Affected:
             - [SYS$LDR]SYS$PKADRIVER.EXE
             - [SYSEXE]SYS$CONFIG.DAT

      o This fix will avoid a bugcheck on a data underrun completion
         code when the SCSI status indicates a reservation conflict.
         The return request is complete when the SCSI message
         SCSI$C_RESERVATION_CONFLICT displays.

           Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE

      o GKDRIVER has a data transfer capability of up to 65535 bytes,
         which limits its functionality with some SCSI devices.

           Images Affected: [SYS$LDR]SYS$GKDRIVER.EXE

      o A generic SCSI device may cause command timeout errors in the
         error log file.

           Images Affected:
             - [SYS$LDR]SYS$DKDRIVER.EXE
             - [SYS$LDR]SYS$GKDRIVER.EXE
             - [SYS$LDR]SYS$MKDRIVER.EXE
             - [SYS$LDR]SYS$PKEDRIVER.EXE

      o When using a SCSI-class driver to send a inquiry command to a
         device on the SCSI bus, if the phase transition timeout value
         is greater than 300 seconds, the SCSI-class driver returns an
         error condition of SS$_BADPARAM to the user and aborts the IO.

           Images Affected:
             - [SYS$LDR]SYS$DKDRIVER.EXE
             - [SYS$LDR]SYS$GKDRIVER.EXE
             - [SYS$LDR]SYS$MKDRIVER.EXE

      o A system can crash with an INCONSTATE, 'Inconsistent I/O
         database' bugcheck. The PKQDRIVER would return errors when it
         could not accept any more commands.

           Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE

      o Mount verification occurs unnecessarily when an HSZ unit's
         'Attention, informational message' error messages are
         received.

           Images Affected: [SYS$LDR]DKDRIVER.EXE

      o Disk error counts exceed 65,0000. The error count was
         decremented for for unit attention when no error was, in fact,
         logged.

           Images Affected: [SYS$LDR]DKDRIVER.EXE

    INSTALLATION NOTES:

    This kit requires a system reboot. Compaq 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.

    All trademarks are the property of their respective owners.

    ---