OpenVMS ALPLAD02_071 OpenVMS Alpha V7.1 - V7.1-1H2 LADDRIVERS ECO Summary

TITLE: OpenVMS ALPLAD02_071 OpenVMS Alpha V7.1 - V7.1-1H2 LADDRIVERS ECO Summary
 
Modification Date:  20-SEP-99
Modification Type:  Updated Kit:  Supersedes ALPLAD01_071

NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.
 
Copyright (c) Compaq Computer Corporation 1999.  All rights reserved.

OP/SYS:     DIGITAL OpenVMS Alpha

COMPONENT:  DADDRIVER  (SYS$DADDRIVER.EXE)                                    
            LADDRIVER  (SYS$LADDRIVER.EXE)                                    
            LASTDRIVER (SYS$LASTDRIVER.EXE)                                   
            MADDRIVER  (SYS$MADDRIVER.EXE)                                    
            ESS$LASTCP.EXE                                              
            ESS$LADCP.EXE 
            ESS$LAD_STARTUP.COM 
            ESS$LAST_STARTUP.COM 
            ESS$STARTUP.COM 

SOURCE:     Compaq Computer Corporation 

ECO INFORMATION:

     ECO Kit Name:  ALPLAD02_071
     ECO Kits Superseded by This ECO Kit:  ALPLAD01_071
     ECO Kit Approximate Size:  1260 Blocks
                    Saveset A - 1260 Blocks

     Kit Applies To:  Alpha V7.1, V7.1-1H1, V7.1-1H2
     System/Cluster Reboot Necessary:  Yes
     Rolling Reboot Supported:  Yes

     Installation Rating:  INSTALL_2
                           2 - To be installed on all systems running
                               the listed versions of OpenVMS and
                               using the following feature:

                                 Infoserver

     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 must also be installed:

         None




ECO KIT SUMMARY:

An ECO kit exists for SYS$DADDRIVER, SYS$LADDRIVER, SYS$LASTDRIVER, and       
SYS$MADDRIVER on OpenVMS Alpha V7.1 through V7.1-1H2.    

PROBLEMS ADDRESSED IN ALPLAD02_071 KIT

     o  LADCP> SHO SERVICES/TAPE crash in MADDRIVER

          If a system has multiple controllers  and  they  are  not  all
          connected  to  the  wire,  then the following (sample) solicit
          command can time out and then crash in MADDRIVER:

          $ MC ESS$LADCP
          LADCP> SHO SERVICES/TAPE


          Image(s) Affected

           -  [SYS$LDR]SYS$MADDRIVER.EXE


     o  MOUNT (or BACKUP)/MEDIA=COMPACT  DEV(x)  mis-handling  density
        setting

          MOUNT/MEDIA=COMPACT DEV(x)  and  BACKUP/MEDIA=COMPACT  do  not
          handle density setting correctly.  Hence, density is not being
          enabled.

          Image(s) Affected

           -  [SYS$LDR]SYS$MADDRIVER.EXE



     o  Service solicitation queues  unsynchronized  (INVEXCEPTN  in
        LASTDRIVER)

          In a multi-processor  environment,  the  service  solicitation
          queues  may  be  accessed  by several processors.  Since these
          queues are not synchronized correctly, they can get corrupted.
          Thus,   the  system  crashes  with  an  INVEXCEPTN  at  around
          LASTDRIVER+3513 in routine LAST$TICK.

          Note:
          LAST  should  not  be  started   on   non-connected   Ethernet
          controllers.  Otherwise, problems with the LADCP> SHOW SERVICE
          command can occur.


          Image(s) Affected:

           -  [SYS$LDR]SYS$LASTDRIVER.EXE


     o  Re-initialize of TZ86 tape times out

          If a tape is initialized on a TZ87 and then put on a TZ86 with
          an  attempt  to  re-initialize  the  tape,  the  TZ86 takes an
          excessive amount of time to determine how to handle the  tape.
          Hence, it times out.

          Image(s) Affected:

           -  [SYS$LDR]SYS$MADDRIVER.EXE


     o  NEWVAL not initialized in routine LADCP_SET

          The BLISS compiler output an error message that NEWVAL is  not
          initialized in routine LADCP_SET.

          Image(s) Affected:

           -  [SYSEXE]ESS$LADCP.EXE


PROBLEMS ADDRESSED BY ALPLAD01_071:

  o  The system crashes in LTDRIVER when SSB is deleted  prematurely
     while an UNLOAD is in progress.

  o  The LASTDRIVER image crashes when it receives an  Advertisement
     (ADV) or Solicit (SOL) message with a negative message length.

  o  In the past,  BIND/TAPE/NOPERMANENT  "tape_service"  created  a
     MADx  device  UCB  that could be deleted once the UCB reference
     count went to zero.  Problems occurred when the UCB was deleted
     due   to  the  use  of  the  /NOPERMANENT  qualifier,  that  is
     multivolume BACKUP.

     Note:  A MAD device is a tape device that  is  attached  to  an
            InfoServer.


INSTALLATION NOTES:

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

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

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

     The images in this kit will not take effect  until  the  system  is
     rebooted.

     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.

Files on this server are as follows:

»alplad02_071.README
»alplad02_071.CHKSUM
»alplad02_071.CVRLET_TXT
»alplad02_071.a-dcx_axpexe
»alplad02_071.CVRLET_TXT