SNA_PRSRV T21E132 DEC SNA Peer Server V1.3 ECO Summary
Copyright (c) Digital Equipment Corporation 1995, 1996. All rights reserved.
PRODUCT: DEC SNA Peer Server V1.3
OP/SYS: Digital UNIX V3.2 or later
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: T21E132
ECO Kits Superseded by This ECO Kit: T21131
ECO Kit Approximate Size: 17786880 Bytes (34740 Blocks)
Kit Applies To: DEC SNA Peer Server V1.3
System/Cluster Reboot Necessary: Yes
ECO KIT SUMMARY:
An ECO kit exists for DEC SNA Peer Server V1.3 on Digital UNIX V3.2 or
later. This kit addresses the following problems:
ECO 02 Description (T21E132):
-----------------------------
The DEC SNA Peer Server Release Notes contain a complete explanation of
this release. Below is a brief description of the problems fixed by this
release.
o Resolved a system crash when token ring giving errors.
When the Peer Server was utilized with a token ring and the token
ring network began to report errors to the Peer Server the Peer
Server would cause a system crash. The characteristics of this
crash were that it would fail freeing an mbuf at line 1342 in module
t21llc/src/t21llc_dlpi_actn.c.
o Resolved problem with passive connections would hang a session.
The Peer Server was not handling GAP V3 passive connections properly
where no USS data was requested by the client. The symptom of this
problem was that the OpenVMS Printer Emulator V1.3 would hang a
session when that session terminated.
o Improved TCP/IP Transport Performance.
When the Peer Server was accessed by an access routine using TCP/IP
as the transport, performance was non-optimal. This was because the
PAI used in the CAD daemon process used write() instead of writev()
when sending TCP/IP messages to the access routines. The Peer
Server now uses the writev() service so that the message header
doesn't get separated from the message body.
o Corrected software version number in transmitted XID.
The Peer Server was sending an obsolete software version number
(V110) in the XID software subvector for the Product Set ID. Now it
sends the correct current version number.
o Prohibited use of permanent TGs that are in the connecting state.
The Peer Server was attempting to a use a permanent TG when it was
in the connecting protocol state in the expectation it would
eventually become active. Even though this is a valid assumption it
is better to give an error and allow the user to go and understand
why the TG hasn't come up fully.
o Prevented SDLC circuits from resetting every inactivity seconds.
If the Peer Server was operated with a product such as MEGAPAC (an
SDLC spoofing product) that generated multiple SNRMs the SDLC
inactivity timer would fire every inactivity timer seconds and reset
the SDLC station with the result that all sessions would be taken
down and have to be reestablished when the station immediately
restarted.
o Fix internal trace so it works on multi-processor systems.
The internal trace facility truncated its output on multi-processor
systems.
o Fix CTF QLLC analysis routine.
CTF would SEGV in some cases when analyzing QLLC trace files.
o Fix GAP version negotiation problem.
If multiple clients connected to the Peer Server simultaneously it
was possible for an incorrect GAP version number to be sent back to
the client.
o Fix assorted memory leaks in t21cad process.
The t21cad processes would fail to return heap memory and threads
resources to the system. This could lead to hanging or unexpected
termination of the t21cad processes.
o Fix incorrect reported byte offset in XID Negotiation Control Vector.
If the Peer Server detected an error in a received XID it would
report an incorrect error byte offset that was always a negative
number.
o Fix memory leak in Common Agent mold process.
Each time an NCL command was issued to the Peer Server the mold
process would grow by about 45kb of virtual memory and utilize more
threads resources. Eventually the mold process would either core
dump or use up all the swap space on the system. This prevented
Peer Server NCL commands from working at all neccessitating either a
restart of the Peer Server or a system boot. This kit includes a
new mold process that will be installed onto the system unless a new
mold has been supplied through a patch to the Digital UNIX base
operating system or the installation of Digital UNIX V3.2g.
o Allow Peer Server to be installed with WAN (X.25) Support V2.0.
The Peer Server would not install correctly if the V2.0 of the
product: Wide Area Networking (WAN) Support for Digital UNIX
(previously known as X.25 for Digital UNIX Systems) was installed.
More information regarding the nature of these problems can be found in
the ECO kit's release notes. Also, previous ECO kit fixes are fully
described, since the ECOs are cumulative fixes.
ECO 01 Description (T21131):
---------------------------
o Resolved a UNIX kernel memory corruption problem.
Prior to ECO-01, the Peer Server might corrupt kernel pool during
outbound session allocation. This problem could result in various
unaligned memory fault crashes with "Unaligned kernel space access
from kernel mode" being prevalent.
This problem could occur in any version of Digital UNIX, however the
new memory allocation scheme in Digital UNIX V3.2C made the problem
more likely to occur.
The problem was resolved by allocating the correct buffer size
required for the connect response message.
INSTALLATION NOTES:
The ECO kit is distributed as a tar file containing the kit which can
be installed using the setld command. The tar file should be unpacked
to a suitable directory and then the setld command issued specifying
that directory as the source of the kit.
For example, if the tar file containing the kit has been copied to
/usr/tmp/t21E132.tar:
# mkdir /usr/tmp/t21E132
# cd /usr/tmp/t21E132
# tar xf /usr/tmp/t21E132.tar
# setld -l .
If the kit is delivered on tap11 then the commands would be:
# mkdir /usr/tmp/t21E132
# cd /usr/tmp/t21E132
# tar x
# setld -l .
Note that this is not an update kit, and the current version of the
Peer Server must be deleted before installing this ECO. Deleting the
current kit will not remove the current setup, but you will have to
rebuild the kernel and reconfigure the kit, and you will need to
redefine any tn3270 server processes. Please see the Release Notes
for more details ("t21_E13-2_release_notes" in T21MGMT132).
Once the kit is installed, you should follow the instructions in the
installation guide for rebuilding the kernel then reboot the system
and configure the kit with the exception that it is not necessary to
rerun the initial configuration utility.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
t21131.README
t21e132.CHKSUM
t21e132.CVRLET_TXT
t21e132.tar
|
