SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
OpenVMS VAXSYSL20_U2055 VAX V5.5-2 SYSLOA/SET TIME ECO Summary

TITLE: OpenVMS VAXSYSL20_U2055 VAX V5.5-2 SYSLOA/SET TIME ECO Summary Modification Date: 29-SEP-1999 Modification Type: DOCUMENTATION: Technical Modification: This kit CANNOT be installed on OpenVMS VAX V5.5-2HF or VAX V5.5-2H4. 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 1998. All rights reserved. OP/SYS: OpenVMS VAX COMPONENT: SYSLOA ERFBRIEF ERFNVAX ERFSHR ERFV14 ERFXRP SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: VAXSYSL20_U2055 ECO Kits Superseded by This ECO Kit: VAXSYSL19_U2055 VAXSYSL18_U2055 VAXSYSL17_U2055 (CSCPAT_1077) VAXSYSL15_U2055 VAXSYSL14_U2055 VAXSYSL13_U2055 (CSCPAT_1076) VAXSYSL12_U2055 VAXSYSL10_U2055 (CSCPAT_1032) ECO Kit Approximate Size: 2160 Blocks Kit Applies To: OpenVMS VAX V5.5-2 System/Cluster Reboot Necessary: Yes Rolling Reboot Supported: Yes Installation Rating: 3 - To be installed on all systems running the listed versions of OpenVMS which are experiencing the problems described. 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 SET TIME and other SYSLOA issues on OpenVMS VAX V5.5-2. Problems addressed in the VAXSYSL20_U2055 kit: o The VAXSYSL19_U2055 remedial kit superseded the VAXSYSL18_U2055 kit but it did not include all the images that were shipped with the VAXSYSL18_U2055 kit nor did it include the descriptions of problems fixed by the VAXSYSL18_U2055 kit. This kit includes those images and descriptions. However, even though these images and descriptions need to be included to maintain a proper supersession stream, there are no new ECO corrections to the images. If you have installed the VAXSYSL18_U2055 and VAXSYSL19_U2055 remedial kits, you do not need to install this kit. Problems addressed in the VAXSYSL19_U2055 kit: o Entering a "SET TIME" command without a specific time has been known to cause intermittant SS$_IVTIME (%SYSTEM-F-IVTIME, invalid time) errors on VAX 7000-600 multiprocessor (SMP) systems. Once this error is returned, subsequent "SET TIME" commands without an explicit time will continue to produce this error. To correct this condition another "SET TIME" comand, with specific time information, must be executed. Problems addressed in the VAXSYSL18_U2055 kit: NOTE: The following SYSLOA*.EXEs are included in this ECO kit and are used with the CPU types shown: SYSLOA1202 VAX 6000-500 SYSLOA1302 VAX 6000-600 SYSLOA1303 VAX 4000-100/100A/105A MicroVAX 3100-90/95 SYSLOA1701 VAX 7000/10000 SYSLOA420 MicroVAX 3100 SYSLOA440 VAXstation 4000-VLC MicroVAX 3100-30/40 SYSLOA46 VAXstation 4000-60 MicroVAX 3100-80 SYSLOA49 VAXstation 4000-90 SYSLOA43 VAXstation 3100 M76 SYSLOA43D VAXstation 3100 M76/GPX SYSLOA43S VAXstation 3100 M76/SPX SYSLOA43W VAXstation 3100 M76 (MONOCHROME) SYSLOA9CC VAX 6000-200/300 SYSLOA9RR VAX 6000-400 *********************** WARNING **************************** * * * If you are going to install this ECO kit on a VAXstation * * 4000 Model 60 or VAXstation 4000 Model 90 system that has * * a TURBOchannel device installed *AND* is a member of a * * VAXcluster, you *MUST* install CSCPAT_1045 on your * * system either before or in the same installation session * * with this ECO. If this ECO is installed on a * * system that meets the requirements mentioned above, * * the system will crash at boot time with an INVEXCEPTN * * bugcheck at STACONFIG+578A if CSCPAT_1045 does not * * exist on the system. * * * * If you install both kits during the same session, * * Digital recommends that you do not reboot between the * * application of the two ECO kits due to the probability * * of a system bugcheck which causes an unbootable system * * if only this ECO is installed. * * * * For more information, please see the following article: * * * * *OpenVMS] CSCPAT_1045 SYSGEN, STACONFIG And * * TURBOchannel ECO Summary * * * ************************************************************** o Previous SYSLOA kits have been combined into one kit. All the problem solutions that were in the kits superseded by VAXSYSL18_U2055 are included in VAXSYSL18_U2055 and apply to versions 5.5-2 and 5.5-2H4 of OpenVMS VAX. o ANALYZE/ERROR returns an ACCVIO while processing a memory error packet. o The VAXstation Model 90 hangs when the VME B board is accessed after reset. o ANALYZE/ERROR report does not call the VAXstation 4000-VLC and MicroVAX 3100-30, -40 a KA45 as it should. Problems addressed in the VAXSYSL17_U2055 kit: o An Access Violation will occur when an FAO System Service call fails due to invalid information in the memory configuration hardware register. This occurs primarily on MicroVAX 3100 Model 90, VAXstation 4000 Model 100 and VAXstation 4000 Model 90 CPUs. o The memory configuration register prints out the memory configuration of the system. On the VAXstation 4000 Model 90, the total size of system memory reported is incorrect. o On the VAXstation 3100 Model 76, incorrect information is reported by the cache error machine check code and the error buffers are formatted incorrectly. This causes difficulty in pinpointing memory errors. o The following time-out error message will appear on the system console if the port is in the XOFFed state too long: %TYPE-F-WRITEERR, error writing SYS$OUTPUT -RMS-F-WER -SYSTEM-F-TIMEOUT %DCL-W-SKPDAT o ANALYZE/ERROR will Access Violate (ACCVIO) while processing a memory error packet which is generated by SYSLOA1303.EXE on the VAXstation 4000 Model 100 or SYSLOA49.EXE on the VAXstation 4000 Model 90. Problems addressed in the VAXSYSL15_U2055 kit: o This kit contains the following fixes for the SYSLOA440 Error Handler on VAXstation 4000-VLC and the MicroVAX 3100 Model 30/80: - All machine check and polled errors are assumed to be cache/bus errors but they are mostly caused by memory parity errors. - No memory error states are saved and logged. - SCSI parity checking is not enabled. - The MSER register bits are defined incorrectly. - Polled errors always cause the system to crash even though polled errors are always recoverable. - Cache data parity errors are not being 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 This kit contains the following fixes for the SYSLOA46 Error Handler on VAXstation 4000 Models 60 and the MicroVAX 3100 Model 80: - 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 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 the VAXstation 4000-VLC and MicroVAX 3100 Models 30/40, memory configuration and memory status information is not displayed. Problems addressed in the VAXSYSL14_U2055 kit: o If a TURBOchannel device does not respond to one of two current TURBOchannel device addresses, a third-party TURBOchannel (TC) module on a VAXstation 4000 Model 90 or VAXstation 4000 Model 60 will not be configured correctly. o Due to changes in the timing on some TURBOchannel hardware, the VAXstation 4000 Model 90 and the VAXstation 4000 Model 60 may hang when certain TURBOchannel options are accessed after a reset. Problems addressed in the VAXSYSL13_U2055 kit: o Normal system operation may be severely disrupted on VAX 7000/10000 systems because the cache error correction routine does not properly correct cache single bit errors. Problems addressed in the VAXSYSL12_U2055 kit: o VAX 7000/10000 systems may crash due to rare occurrences of ECC errors in the CPU module back-up cache. These errors will not corrupt data and will be shown in the OpenVMS error log 'SYS$ERRORLOG:ERRLOG.SYS'. o On VAX 6000 systems, the CONNECT command for the VME device driver might cause the system to crash. SYSGEN requires the INIT flag to be set in the ADP by SYSLOA before it can connect the VME device driver. When this does not happen, the system will crash. o VAX 6000/7000 systems do not support IRQ6 interrupts. Problems addressed in the VAXSYSL10_U2055 kit: o When memory errors are encountered on a VAXstation 3100, the system will crash and will not reload without manual intervention. CDAL parity errors are incorrectly logged in the error report. The SYSLOA420 image included in this ECO correctly handles CDAL parity errors and improves the memory error handling. INSTALLATION NOTES: 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. If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed.



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

vaxsysl20_u2055.README
vaxsysl20_u2055.CHKSUM
vaxsysl20_u2055.CVRLET_TXT
vaxsysl20_u2055.a-dcx_vaxexe
vaxsysl20_u2055.CVRLET_TXT

privacy and legal statement