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 VAXLAT02_061 OpenVMS VAX V6.1 LTDRIVER/LATACP ECO Summary

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 COMPONENT: LAT, LTDRIVER SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: VAXLAT02_061 ECO Kits Superseded by This ECO Kit: VAXLAT01_061 ECO Kit Approximate Size: 300 Blocks Saveset A - 288 Blocks Kit Applies To: OpenVMS VAX V6.1 System/Cluster Reboot Necessary: Yes Installation Rating: 2 - To be installed on all systems running the listed version(s) of OpenVMS and using the following feature: LAT NOTE: In order to receive the full fixes listed in this kit, the following remedial kits also need to be installed: None ECO KIT SUMMARY: An ECO kit exists for LAT on OpenVMS VAX V6.1. This kit addresses the following problems: PROBLEMS ADDRESSED IN VAXLAT02_061 KIT o VCRP packets are being overwritten. o A CREATE LINE LINK$NAME/DEV=XXA0: command in LATCP can crash the system. o After executing the following commands: LATCP> CREATE SERVICE SERVICE1/APPL LATCP> CREATE SERVICE SERVICE2/APPL LATCP> CREATE SERVICE SERVICE3/APPL LATCP> DELETE SERVICE SERVICE2 LATCP> SET SERVICE SERVICE3/STATIC_RATING=1 the static ratings for services following SERVICE2 can not be changed. PROBLEMS ADDRESSED IN VAXLAT01_061: o System crash due to memory being allocated twice during TSM TEST LAT command. o System crash due to dedicated port queue corruption o The LATACP process loops, blocking further LAT connections o SET HOST/LAT connections hang when connected to OSF systems. o System crash during link deletion and/or creation. o CPUSPINWAIT BUGCHECKs o Connecting to a dedicated port for application service results in a protocol violation and the "invalid credit" counter being incremented. o Fix possible CPUSPINWAIT crashes in PORT_CANCEL. o The LAT architecture describes the response timer field in two places. Once, it is described as a value during solicitation. Secondarily, it also describes how to use that value to generate a random number timeout period within acceptable limits. In one place, "10ms units" are referred to and in the other, "seconds" is referred to as the unit of time. LTDEF thought the "10ms units" was the correct value for a LAT message when "seconds" is needed. o In a SET HOST /LAT session, during certain circumstances of lost messages, LTDRIVER is erroneously setting the RRF bit in the master message without checking to see if the circuit is doing delayed acknowledgments. RRF should not be set unless a circuit has successfully negotiated delayed ACKS o LATACP crashes with PGFIPLHI o LTDRIVER crashes with INVEXCEPTN o Some applications use break, through the system service, to write to their numerous terminals at the same time. When LATCP is running, the management LTA device created by LATCP is also broadcast to. This slows done the application to the point where the application exhausts its byte limit o An MC LATCP CREATE PORT command with an invalid device name will crash the system. 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 VMScluster, the entire



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

vaxlat02_061.README
vaxlat02_061.CHKSUM
vaxlat02_061.CVRLET_TXT
vaxlat02_061.a-dcx_vaxexe

privacy and legal statement