Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
HP Services Software Patches - vaxlad02_061
 
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) Digital Equipment Corporation 1998.  All rights reserved.

OP/SYS:     OpenVMS VAX

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

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXLAD02_061
     ECO Kits Superseded by This ECO Kit:  VAXLAD01_061 (Not Released for Use)
     ECO Kit Approximate Size:  411 Blocks
                    Saveset A - 396 Blocks

     Kit Applies To:  OpenVMS VAX V6.1
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:   2 - To be installed on all systems running
                                the listed version 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 should also be installed:

        None


ECO KIT SUMMARY:

An ECO kit exists for SYS$DADDRIVER, SYS$LADDRIVER, SYS$LASTDRIVER, and       
SYS$MADDRIVER on OpenVMS VAX V6.1.  This kit addresses the following problems:


PROBLEMS ADDRESSED IN VAXLAD02_061 KIT:

  o  UCB$L_DEVCHAR2 characteristics bits are not  defined  correctly    
     when the template UCB is created.  This problem causes SECURITY    
     to crash the system and  causes  LADCP>  BIND  SERVICE/TAPE  to    
     prefix device name, MADx, with a node name or allocation class.    
     This  result  is  inconsistent  with  the  DAD  device   naming    
     convention.                                                        
                                                                    
  o  The occasional packet transmitted  by  EWDRIVER  had  a  source    
     address  and protocol type of zeros, which are discarded by the    
     receiver.  The booting system then retransmitted the  packet  3    
     seconds  later.   However, since it is handling only 10 packets    
     per second, the system booted very slowly.                         
                                                                   
  o  If LADDRIVER parses connection (or solicitation) messages  that    
     have  the sign bit set in the service class (an invalid value),    
     the OpenVMS system will crash with an INVEXCEPTN bugcheck.         
                                                                    
  o  The system crashes in LTDRIVER when SSB is deleted  prematurely    
     while an UNLOAD is in progress.                                    
                                                                    
  o  LASTDRIVER/DADDRIVER/MADDRIVER fixes:                              
                                                                    
     1.  Typing a CTRL/Y  at  a  certain  instance  could  cause  an    
         IO$_PACKACK  function  to a MAD device to be canceled.  The    
         result could eventually be that the system crashes  in  I/O    
         post processing.                                               
                                                                    
     2.  LADCP BIND/UNIT=x will cause a duplicate UCB unit number to    
         be  generated  if the unit number specified is greater then    
         the seed unit number.  This problem  can  happen  for  both    
         DADDRIVER and MADDRIVER.                                       
                                                                   
  o  LASTDRIVER crashes when it receives a run  message  in  circuit    
     stalled.                                                           


PROBLEMS ADDRESSED IN THE VAXLAD01_061 KIT:

  o  Routine READ_BFRS_DONE_WITH, of module LADDRIVER,  attempts  to     
     remove  the  IOP from the active queue.  If the active queue is     
     zero, then the request has already been aborted and the  system     
     crashes.                                                            
                                                                     
     In a different system crash scenario, if routine LAD$REQUEST_CU     
     is called with the wrong function, or an IOP cannot be acquired     
     due to some resource allocation failure, the attempt is made to     
     re-insert  the  IOP on the FREE_IOP_Q.  The system crashes with     
     INVEXCEPTN because the IOP address is invalid.                      
                                                                     
  o  The    SWEEP_CACHE    routine    was    being    called    from     
     LAD$END_SESSION_CU  routine with the wrong register pointing at     
     the server descriptor block.  This prevented the  cache  blocks     
     associated   with   the  session  to  be  terminated,  but  not     
     invalidated correctly.  Therefore, these blocks remained in the     
     cache.                                                              
                                                                     
     Subsequently,  the  virtual  disk  could  be  dismounted,   and     
     modified by PCDISK.  When the virtual disk was remounted again,     
     the blocks held in cache did not reflect the modifications, and     
     data corruption occurred.                                           
                                                                     
  o  Container file corruption for PATHWORKS                             


INSTALLATION NOTES:

The images in this kit will not take effect until the system is
rebooted.  If there are other nodes in the VMScluster, they must 
also be rebooted in order to make use of the new images.  

If it is not possible or convenient to reboot the entire cluster at 
Files on this server are as follows:
Files on this server are as follows:
»vaxlad02_061.README
»vaxlad02_061.CHKSUM
»vaxlad02_061.CVRLET_TXT
»vaxlad02_061.a-dcx_vaxexe
privacy statement using this site means you accept its terms