Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
ALPLAT05_061 OpenVMS Alpha V6.1 LTDRIVER/LATACP ECO Summary
Copyright (c) Digital Equipment Corporation 1998. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: LAT, LTDRIVER
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ALPLAT05_061
ECO Kits Superseded by This ECO Kit: ALPLAT04_061
ECO Kit Approximate Size: 1078 Blocks
Saveset A - 1062 Blocks
Kit Applies To: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2
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(s):
LAT
ECO KIT SUMMARY:
An ECO kit exists for LAT on OpenVMS Alpha V6.1 through V6.1-1H2
This kit addresses the following problems:
PROBLEMS ADDRESSED IN ALPLAT05_061:
o VCRP packets are being overwritten.
o 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 ALPLAT04_061 KIT:
o Item list verification routines caused an ACCVIO
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.
PROBLEMS ADDRESSED IN ALPLAT01_062 FOR OPENVMS ALPHA V6.1 through V6.1-1H2:
o Fix possible CPUSPINWAIT crashes and another crash during LAT
$QIO postprocessing.
o System can only sustain about 125 LAT X sessions to various VXT
2000s on the network. Some customers have more than 125 VXT
2000s and not all users can connect to larger OpenVMS systems.
o If LTDRIVER times out a virtual circuit, it will build and
transmit a LAT Stop message. If a session on the virtual
circuit attempts to write data while the datalink layer owns
the Stop message (i.e. the message is on the "to be
transmitted" queue), the system will crash in routine
LT$DECLARE_CIRC_EVENT.
o In the following cases, the print symbiont prints an unwanted
form feed after a print job:
1. Output ends exactly at the end of the page 2. File printed
with a /PASSALL switch ends with a form feed
o Possible CPUSPINWAIT crashes in LT$PORT_CANCEL.
o Fix LATACP hangs due to improper synchronization of queuing to
LATACP.
PROBLEMS ADDRESSED IN AXPLAT03_061 KIT:
o If a user connects and disconnects to an LTA device too quickly
the following error messages will be generated on the terminal
server:
Local -207- Protocol violation
or
Local -226- Protocol violation
This will cause every user connected to that host to be
disconnected.
PROBLEMS ADDRESSED IN AXPLAT02_061 KIT:
o FDDI controllers are slower than Ethernet controllers when it
comes to asynchronous device control events. Because of the
CPU speed of Alpha systems, it is possible for a user to create
a LAT link on an FDDI controller, delete it and then delete it
a 2nd time thus causing a system crash.
PROBLEMS ADDRESSED IN AXPLAT01_061 KIT:
o In V6.1, LATACP was modified to set the LAT rating to 0 if all
OpenVMS LMF units have been consumed. Unfortunately, LATACP
only checked the OpenVMS ALPHA LMF units. It should also check
OpenVMS ALPHA USER. LATACP has been changed to check the same
LMF PAKs that LOGINOUT checks before determining if all OpenVMS
LMF units have been consumed.
NOTE: A LAT rating of 0 does not mean that LAT connections are
disabled. It is simply the lowest possible rating that LAT
nodes will advertise (meaning the system is 'not very
available'). This bug hampers LAT load balancing in an OpenVMS
cluster.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the LAT-DECSERVER or OPENVMS databases. To view these articles, open
the appropriate product database and perform a query using either of
the following search strings: 'ALPLAT05_061' or 'ALPLAT'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
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
cluster should be rebooted.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| LATACP.EXE | 066E485A | V2.0-172C | 7-NOV-1997 |
| | | 11:29:48.22 |
+----------------------------+----------+-----------------+--------------+
| LATCP.EXE | 6F834350 | V2.0-041 | 7-NOV-1997 |
| | | 11:29:55.28 |
+----------------------------+----------+-----------------+--------------+
| SYS$LTDRIVER.EXE | 667A57FD | X-3 | 7-NOV-1997 |
| | | 11:29:41.45 |
+----------------------------+----------+-----------------+--------------+
|
