OpenVMS/LAT CSCPAT_0511 LAT ECO Summary
Copyright (c) Digital Equipment Corporation 1993, 1994. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENT: LAT
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
CSCPAT Kit: CSCPAT_0511 V3.6 (CSCPAT_0511036)
CSCPAT Kit Size: 2160 Blocks
Engineering Cross Reference: VAXLAT02_U2055
Kit Applies To: OpenVMS VAX V5.4, V5.4-1, V5.4-2, V5.4-3,
V5.5, V5.5-1, V5.5-2, V5.5-2H4
System Reboot Necessary: Yes
ECO KIT SUMMARY:
An ECO (patch) kit exists for LAT on OpenVMS VAX V5.4 through V5.5-2[H4].
This kit addresses the following problems:
o OpenVMS VAX does not recognize any speed above 38400 kbps and
will report a terminal speed of 0 if set to 57600 kbps on
terminal server.
o If a system manager creates several services (sometimes in
excess of 20 LAT services) on an OpenVMS VAX system, it is
possible that the system may crash if the resulting LAT Service
Announcement message is between 1488 and 1500 bytes in size.
o If the LAT node state is set to "shut", OpenVMS will still
allow new incoming connections. This is incorrect behavior as
the LATCP documentation states that the "shut" state allows
existing connections to continue and operate but no new
connections are allowed.
o If a system manager creates several services (sometimes in
excess of 20 LAT services) on an OpenVMS VAX system, it is
possible that the system may crash if the resulting LAT Service
Announcement message is between 1488 and 1500 bytes in size.
o If the LAT node state is set to "shut", OpenVMS will still
allow new incoming connections. This is incorrect behavior as
the LATCP documentation states that the "shut" state allows
existing connections to continue and operate but no new
connections are allowed.
o If a user program issues a POSIX selective cancel operation for
an OpenVMS VAX LAT device, this operation will return "function
not supported".
V3.5 addressed:
o During the execution of the LATCP CREATE LINK /DECNET
command, the following error might be returned:
%SYSTEM-F-BADPARAM, bad parameter value
Another possibility is that there would be no LINK present as
indicated by the LATCP SHOW LINK command returning the
following error:
%LAT-W-CMDERROR, error reported by command executor
-SYSTEM-W-NOMOREDEV, no more devices
o When the LAT protocol is started on a FDDI controller, the
datalink address associated will not be the DECnet Phase IV
address of AA-00-04-00-nn-nn. Instead it will be the hardware
controller's station address which is in the form of
08-00-2B-nn-nn-nn. This can cause a problem with Pathworks
clients who are not listening to the multicasted LAT service
announcement messages. They are expecting to utilize the
AA-00-04-00-nn-nn address form.
o LAT messages may not be exchanged between two FDDI rings
that are connected by an Ethernet. This behavior may exhibit
itself by the LAT session being stopped due to the retransmit
limit having been exceeded.
o A system may crash with an INVEXCEPTN bugcheck at or around
LTDRIVER + 250D in a SMP environment.
o When using a dedicated port with application LAT services, the
LATCP SHOW SERVICE command can incorrectly list dedicated
ports for the wrong application services.
o When a user performs a SET HOST /LAT to an Infoserver or another
system that requires a password for the LAT service, the message
%LAT-I-DISCONNECTED, session disconnected from SERVICE
-LAT-I-END, control returned to node NODE_NAME
is returned after the user provides the password.
o An OpenVMS VAX system has non-paged pool exhausted and most of
the blocks in non-paged pool contain LAT service announcement
messages. Under certain circumstances, a VMScluster system
could crash with a CLUEXIT type of bugcheck.
o When the system is attempting to transmit a LAT reject slot to a
remote terminal server, it crashes because the virtual circuit
for the connection has already been deleted. This crash is
mostly seen with systems that have many connections from an
Emulex terminal server.
o The system crashes with INCONSTATE in LTDRIVER while attempting
to transmit a LAT run message.
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.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
cscpat_0511036_lat.README
cscpat_0511036.CHKSUM
cscpat_0511036.a-dcx_vaxexe
|
