HP Services Software Patches - vaxsysl11_u1055_sysloa

 
Copyright (c) Digital Equipment Corporation 1994, 1995.  All rights 
reserved.

OP/SYS:     OpenVMS VAX                                                       
                                                                              
COMPONENTS: SYSLOA and Error Formatter - ERFSHR.EXE
                                         ERFV14.EXE 
                                         ERFXRP.EXE
                                         SYSLOA440.EXE
                                         SYSLOA46.EXE

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXSYSL11_U1055
     ECO Kits Superseded by This ECO Kit:  VAXSYSL10_U1055
                                           SYSLOA$06_U1055 
     ECO Kit Approximate Size:  600 Blocks     
     Kit Applies To:  OpenVMS VAX V5.5, V5.5-1
     System Reboot Necessary:  Yes 

     NOTE:  The following SYSLOA*.EXEs are included in this                   
            ECO kit and are used with the CPU types shown:                    

            SYSLOA440     VAXstation 4000-VLC
                          MicroVAX 3100-30, 40
            SYSLOA46      VAXstation 4000-60
                          MicroVAX 3100-80

ECO KIT SUMMARY:

An ECO kit exists for SYSLOA and Error Formatter on OpenVMS 
VAX 5.5 through V5.5-1. This kit addresses the following problems:           

Problems addressed in the VAXSYSL11_U1055 kit: 

  o  After installing VAXSYSL10_U1055, the DCL command 
     "ANALYZE/ERROR" produces useless information about
     parity errors for the VAXstation 4000-VLC, 
     MicroVAX 3100-30, and MicroVAX 3100-40. 

  o  The "ANALYZE/ERROR" report does not label the VAXstation 4000-VLC,
     MicroVAX 3100-30, and the MicroVAX 3100-40 as KA45 as it should.  
	
     In addition, VAXstation 4000-60, and MicroVAX 3100-80 are labeled  
     as a KA460 in the errorlogs.  The VAXstation 4000-60 should be 
     labeled as a KA46. The MicroVAX 3100-80 should be labeled KA47.


Problems addressed in the VAXSYSL10_U1055 kit:

  o  If the console port is put into the XOFFed state too long,
     the following time out error message will be displayed on
     the console:

        %TYPE-F-WRITEERR, error writing SYS$OUTPUT
        -RMS-F-WER
        -SYSTEM-F-TIMEOUT
        %DCL-W-SKPDAT

     The error count for device OPA0 will also be incremented.


Problems addressed in the SYSLOA$06_U1055 kit: 

  o  VAXstation 4000 Model 60 workstations and MicroVAX 3100 Model
     30/40/80 servers crash every 11 minutes after encountering 
     memory errors. The combination of a hardware problem and 
     a software problem in the machine error routine invalidates 
     the error log and makes it impossible to find the bad       
     memory component.  

  o  SYSLOA440 corresponds to the VAXstation 4000-VLC and MicroVAX
     Model 3100 Models 30 and 40.  The error handler problems for
     these systems are addressed as follows:

          -  All machine check and polled errors are assumed to be
             cache/bus errors but they are usually memory parity
             errors.

          -  No memory error states are saved and logged.

          -  The MSER register bits are defined incorrectly.

          -  Polled errors always cause system crashes even though
             the errors are always recoverable.

          -  Cache data parity errors are not checked properly
             in the READ_ERRORS routine.

          -  Crash dumps trip across memory locations when a
             parity error occurs and cause the system to hang.

          -  Network parity checking is set twice in the EXE$INIPROCREG
             routine of ERRSUB440 resulting in no SCSI parity checking.

  o  SYSLOA46 corresponds to the VAXstation 4000 Model 60 and the
     MicroVAX 3100 Model 80.  The error handler problems for these
     systems are addressed as follows:

          -  TRAP2 is set in PCSTS causing a fatal bugcheck under
             RE_HANDLER since PCSTS flags are not cleared prior to
             exiting the error handler.

          -  Memory FRU ID is not calculated correctly in FIND_BAD_SIMM
             and MEM_CONFIG if the address is greater than 2800000 hex.

          -  CRD buffer is defined to be twice as large as it should be.

          -  Cache data parity errors are not checked properly in the
             CE_HANDLER routine.

          -  Crash dumps trip across memory locations when a parity error
             occurs and cause the system to hang.

          -  In order to isolate to a single SIMM under RE_HANDLER,
             MEMERR <2> needs to be set if VA <2> is set in the machine
             check stack frame.

          -  When threshold is exceeded for soft (INT54) memory
             parity errors, a message is output indicating that the
             2nd level cache is being disabled.

  o  On VAXstation 4000-VLC and MicroVAX 3100 Models 30/40,
     memory configuration and memory error status information
     is not displayed.

  o  The errorlog entries for uncorrectable memory errors do not
     contain the failing memory's physical address in the MEMERR
     register.  This problem occurs on VAXstation 4000 Model 60
     workstations and MicroVAX 3100 Model 30/40/80 servers.
                                                                              
     This problem is fixed in OpenVMS VAX V5.5-1.       


  o  The file LOGGER.B32 contains translations which print  the
     proper  name  of  the  system at the top of the entry
     For example, KA45, KA46, KA47, KA48. 


INSTALLATION NOTES:

In order for the corrections in this kit to take effect, the system           
must be rebooted.  If the system is a member of a VAXcluster, the             
entire cluster should be rebooted.         

Files on this server are as follows:

»vaxsysl11_u1055_sysloa.README
»vaxsysl11_u1055.CHKSUM
»vaxsysl11_u1055.a-dcx_vaxexe