DEC TCP/IP UCXEC05-031 TCP/IP V3.1 for OPENVMS VAX/AXP ECO Summary
Copyright (c) Digital Equipment Corporation 1994. All rights reserved.
PRODUCT: DEC TCP/IP Services V3.1 for OpenVMS VAX
DEC TCP/IP Services V3.1 for OpenVMS AXP
OP/SYS: OpenVMS VAX
OpenVMS AXP
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: UCXECO5-031
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 39,100 Blocks
Kit Applies To: OpenVMS VAX V5.5 and higher
OpenVMS AXP V1.5, V6.1
System Reboot Necessary: Yes
ECO KIT SUMMARY:
An ECO kit exists for DEC TCP/IP Services V3.1 on OpenVMS VAX V5.5
and higher and OpenVMS AXP V1.5 through V6.1. This kit addresses
the following problems. If more detailed information is needed,
please see the Release Notes in the kit.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 Kernel images
----------------------------------------------------------------------------
ECO 1 Updates:
--------------
ECO A 27-May-1994 AXP and VAX
Images:
UCX$BGDriver.EXE UCX T3.1-32B
The system may ACCVIO in SetMode processing and subsequently
crash because access to socket structures is synchronized
at IPL 8.
ECO B 24-Jun-1994 AXP and VAX
Images:
UCX$BGDriver.EXE
UCX$INTERNET_SERVICES.EXE
UCX$INTERNET_SERVICES_SEC.EXE
UCX$INETACP.EXE
1. Security driver crashes occur when the @ip_secvec$l_ip_output
routine returns an error status.
2. The security driver swapped r4 and r6 in calls to
@ip_secvec$l_ip_input with respect to the V2.0 behavior.
3. The proxy cache was not searched correctly when wildcard
proxies were involved. This led to proxies which did
not appear to be dynamically loaded, even though they were,
and non-wildcard proxies were not found when similar
wildcard proxies existed for different usernames.
ECO C 27-Jun-1994 AXP and VAX
Images:
UCX$BGDriver.EXE
UCX$INTERNET_SERVICES.EXE
UCX$INTERNET_SERVICES_SEC.EXE
When the partner for a TNDRIVER connection became unreachable,
the system would intermittently hang and loop at a high IPL.
ECO 2 Updates:
--------------
There were no additional changes to this facility in ECO 2
ECO 3 Updates:
---------------
ECO D 19-Jul-1994 AXP and VAX
Images:
UCX$INETACP.EXE UCX V3.1-32D
1. System crashes occurred in INETACP_REXEC_ABORT_AST_CONT
due to referencing a REQCB that had been previously
deallocated.
2. System crashes due to misuse of a register might occur,
when the same register is used to contain a channel number
and the address of a descriptor.
3. The system crashes during UCX shutdown in an AST
delivered to the INET_ACP, if reference is made to
the INETCB after it has been deallocated.
ECO 4 Updates:
--------------
ECO E 10-Aug-1994 AXP and VAX
Images:
UCX$BGDriver.EXE UCX V3.1-32E
UCX$INTERNET_SERVICES.EXE UCX V3.1-32E
UCX$INTERNET_SERVICES_SEC.EXE UCX V3.1-32E
Memory corruption occurs when ACCEPT completes after
ACCEPTER BG device has been deassigned, but before the
LISTENER BG device is deassigned.
ECO F 11-Aug-1994 AXP and VAX
Images:
UCX$BGDriver.EXE UCX V3.1-32F
UCX$INTERNET_SERVICES.EXE UCX V3.1-32F
UCX$INTERNET_SERVICES_SEC.EXE UCX V3.1-32F
Setting the minimum number of large buffers too high (more
than 13 with FDDI-size buffers, or more than 31 otherwise)
could cause memory corruption and a subsequent system crash.
ECO G 30-Aug-1994 VAX Only
Images:
UCX$INTERNET_SERVICES.EXE UCX V3.1-32G
UCX$INTERNET_SERVICES_V6.EXE UCX V3.1-32G
UCX$INTERNET_SERVICES_SEC.EXE UCX V3.1-32G
UCX$INTERNET_SERVICES_SEC_V6.EXE UCX V3.1-32G
UCX$INETACP.EXE UCX V3.1-32G
The TCP initial sequence number was being improperly reset
every time a new TCP connection was initiated. This problem
was most visible when using the UCX RSH client to repeatedly
execute commands on a remote host.
**************************************************************
* WARNING *
* *
* Be sure to copy this new UCX$INETACP.EXE image when *
* installing this update. If you take only the *
* UCX$INTERNET_SERVICES image, UCX will not function *
* properly due to shifted data structures. *
**************************************************************
ECO H 7-Sep-1994 AXP and VAX
Images:
UCX$INTERNET_SERVICES*.EXE UCX V3.1-32H
UCX$BGDRIVER*.EXE UCX V3.1-32H
The service limit was not properly enforced for UDP NOLISTEN
services, such as NFS. This led, on occasion, to the startup
of multiple NFS server processes even when the service limit
was set to 1.
ECO 5 Updates:
--------------
ECO I 19-Sep-1994 AXP only
Images:
UCX$BGDRIVER*.EXE UCX V3.1-32I
Use of the shutdown() function with a direction code of 0
(receive only) would result in an error being returned,
with SS$_ABORT in the OpenVMS-style status and garbage
in the UNIX[R] style error, even though the function
actually worked properly.
ECO K 3-Oct-1994 AXP and VAX
Images:
UCX$BGDriver.EXE UCX V3.1-32K (Alpha)
UCX$INTERNET_SERVICES.EXE UCX V3.1-32K
UCX$INTERNET_SERVICES_V6.EXE UCX V3.1-32K
UCX$INTERNET_SERVICES_SEC.EXE UCX V3.1-32K
UCX$INTERNET_SERVICES_SEC_V6.EXE UCX V3.1-32K
UCX$INETACP.EXE UCX V3.1-32K
1. System crash with KRNLSTAKNV.
2. System crash with SPLRSTERR, Spinlock to be conditionally released
is not owned.
ECO L 5-Oct-1994 AXP and VAX
Images:
UCX$BGDriver.EXE UCX V3.1-32L (Alpha)
UCX$INTERNET_SERVICES.EXE UCX V3.1-32L
UCX$INTERNET_SERVICES_V6.EXE UCX V3.1-32L
UCX$INTERNET_SERVICES_SEC.EXE UCX V3.1-32L
UCX$INTERNET_SERVICES_SEC_V6.EXE UCX V3.1-32L
Simultaneous use of select and attention ASTs on the same UCB
will result in a system crash.
ECO M 20-Oct-1994 AXP and VAX
Images:
UCX$INETACP.EXE UCX V3.1-32M
1. Disabling an active UDP Listen service, such as BOOTP,
might also eliminate the listener device for another
service.
2. When using the CASE_INSENSITIVE flag with the RSH service,
usernames containing numeric characters were not found in
the proxy cache.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 UCX$INETDRIVER.EXE
----------------------------------------------------------------------------
ECO 1 Updates:
--------------
ECO A 26-May-1994 AXP and VAX
Images:
UCX$INETDRIVER.EXE UCX 3.1-32A
INET device units are not deleted on final deassignment.
ECO 4 Updates:
--------------
ECO B 12-Sep-1994 AXP and VAX
Images:
UCX$INETDRIVER.EXE UCX V3.1-32B
Multiprocessor crashes on $CANCEL or $DASSGN in INETDRIVER
may occur. The bugcheck is either SPLRELERR or SPLIPLLOW.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 UCX$TNDRIVER.EXE
----------------------------------------------------------------------------
ECO 4 Updates:
--------------
ECO A 1-August-1994
Images:
UCX$TNDRIVER.EXE UCX V3.1-32A
System crashes on SMP may occur.
ECO B 9-August-1994
ECO-A was not built correctly, ECO-B fixes this.
telnet.com uses, libr/replace lib$:ucx$tn_server.olb
obj$:ucx$tn_server_*.obj
When obj$ is a search list, the .obj in [obj_pat] are
replaced first and they get overridden by the .obj in [obj]
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 UCX$TELNET.EXE
----------------------------------------------------------------------------
ECO 5 Updates:
--------------
ECO A 1-August-1994
Images:
UCX$TNDRIVER.EXE UCX V3.1-32A
System crashes on SMP may still occur.
ECO B 9-August-1994
Images:
UCX$TNDRIVER.EXE UCX V3.1-32B
ECO-A was not built correctly, ECO-B fixes this.
telnet.com uses, libr/replace lib$:ucx$tn_server.olb
obj$:ucx$tn_server_*.obj
When obj$ is a search list, the .obj in [obj_pat] are
replaced first and they get overridden by the .obj in [obj]
ECO C 3-October-1994
Images:
UCX$TELNET.EXE UCX V3.1-32C
Telneting from MEP-VT via a 3270 connection caused an error of
"%NONAME-W-NOMSG, Message number 00000000"
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 UCX$TFTP.EXE
----------------------------------------------------------------------------
ECO 4 Updates:
--------------
ECO A 01-Sep-1994 AXP/VAX
Images:
UCX$TFTP.EXE V3.1-32A
Error handling was poor and multithreading techniques occurred
that caused a timeout/resend to fail. Sending to a non-existent
destination port appears to produce a -F-PROTOCOL error.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 UCX$FTP.EXE, UCX$FTPC.EXE, and UCX$FTPD.EXE
----------------------------------------------------------------------------
ECO 1 Updates:
--------------
ECO A 25-May-1994 AXP and VAX
Images:
UCX$FTP.EXE UCX V3.1-32A
UCX$FTPC.EXE UCX V3.1-32A
UCX$FTPD.EXE UCX V3.1-32A
1. An extra reply message which caused client and server
command synchronization loss might be sent by the FTP
server during image mode transfers.
2. FTP MGET fails if the full path name is specified.
3. If the path name was specified using FTP GET, it would
copy the file and use the full pathname as the file name.
4. FTP does not retrieve files in a subdirectory when
performing an mget of a directory which includes a
directory file.
5. FTP get incorrectly expanding wild card characters.
6. Confusion between get and mget capabilities.
ECO 5 Updates:
--------------
ECO B 29-Sep-1994 AXP and VAX
Images:
UCX$FTP.EXE UCX V3.1-32B
UCX$FTPC.EXE UCX V3.1-32B
UCX$FTPD.EXE UCX V3.1-32B
1. Binary files were truncated during File transfer in
image (binary) mode between two ftp nodes if the target
filespec contained a nodename of a third node. This
was caused by the transfer occurring over DECnet on
the target side and was manifest only if the file size
was not an exact multiple of 512 bytes.
2. The FTP command line switches /USER, /PASSWORD, and
/INPUT were not being recognized or used properly.
3. The FTP system could not be run from a command procedure.
4. The "sendport" command fails.
5. The PASV command hangs up the session. The FTP client
session was hanging waiting for a reply from the FTP
server.
6. If the /FDL switch was used while doing a "put" or "get"
command, a "Link Disconnect" error message was received.
This occurred because a parsing error at the FTP client
propagated to the FTP server and caused the FTP server
to ACCVIO.
7. The command ': DIR/FULL' produced truncated output. It
did not list all the files currently in the directory.
This occurred because the initial count of the number of
files in the directory was not zeroed correctly before
the listing was started in the server.
8. The FTP server did not properly report errors caused
by RMS back to the client and did not use the proper
reply codes according to the RFC.
ADDED or CHANGED Functionality:
a. The "DIR" command had been changed to give an output
similar to "ls" instead of a "FULL" listing. Due to
recommendations from end users, it has been changed
back to its original form to produce a "FULL" listing.
The command line switch "/BRIEF" has been added to
produce an output similar to "ls".
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 SMTP Mail Facility
----------------------------------------------------------------------------
ECO 1 Updates:
--------------
ECO A 9-Jun-1994 VAX/AXP
Images:
UCX$SMTP_MAILSHR.EXE
UCX$SMTP_RECEIVER.EXE
UCX$SMTP_SYMBIONT.EXE
UCX$SMTP_PARSESHR.EXE (VAX only)
UCX$SMTP_PARSESHR_TV.EXE (AXP only)
UCX$UUENCODE.EXE
UCX$UUDECODE.EXE
1. Found another symbiont memory leak.
2. SMTP receiver ACCVIOs with address in MAIL From:<>
command that includes source route, for example:
<@PSUVM.PSU.EDU:owner-acm-l@KENTVM.KENT.EDU>
3. SMTP receiver ACCVIOs with an RFC header that exceeds
1000 characters in length. A long To: header was the
only known cause of this.
4. If mail was sent to a UCX system with a quoted local
part (i.e., "NODE::USER"@host.com) and the receiving
UCX host's SMTP relay option was not enabled, the mail
would be accepted by the UCX SMTP receiver and would
be bounced later by the symbiont with an RMS "record
not found" error.
ECO 2 Updates:
--------------
There were no additional changes to this facility in ECO 2
ECO 3 Updates:
--------------
ECO B 28-Jul-1994 VAX/AXP
Images:
UCX$SMTP_MAILSHR.EXE UCX V3.1-32B
UCX$SMTP_RECEIVER.EXE UCX V3.1-32B
UCX$SMTP_SYMBIONT.EXE UCX V3.1-32B
UCX$SMTP_PARSESHR.EXE (VAX only) UCX V3.1-32B
UCX$SMTP_PARSESHR_TV.EXE (AXP only) UCX V3.1-32B
UCX$UUENCODE.EXE UCX V3.1-32B
UCX$UUDECODE.EXE UCX V3.1-32B
1. The SMTP symbiont redefines SYS$SCRATCH in system
table.
2. If an attempt to send a file via SMTP with MAIL/NOEDIT
was made *and* any DECnet address was encountered before
an SMTP address, an RMS-F-IOP error would occur at the
MAIL> prompt. This would happen most commonly if:
·
- A VMS Mail distribution list was used where any
DECnet address preceded an SMTP address.
- A user in a VMS distribution list had their mail
forwarded via DECnet and an SMTP address followed
this user in the list.
- The VMS Mail To: field was a DECnet address and the
CC: field was an SMTP address.
2. If SMTP mail came in for a user who had forwarded his
mail to SMTP%... *and* the substitute domain was set,
the substitute domain information would be included
in the relayed mail From and Return-Path RFC headers.
ECO 4 Updates:
--------------
ECO C 9-Aug-1994 VAX/AXP
1. If the SMTP configuration database relay option was not
set, all incoming SMTP mail to users who had forwarded
their mail was bounced. This occurred when users made
use of the 'MAIL> SET FORWARD' command when the relay
option was not set.
2. UCX SMTP was unable to deliver mail to a recipient (i.e.,
the SMTP address local part) that contained a period. An
example of the type of address that would bounce is:
To: G.Palmer@xyz_corp.com
^
|
+---<--- This period causes problems.
3. UCX SMTP created an entirely new block of RFC headers
when it relayed mail after a user had done a SET
FORWARD. These headers became lost inside the plain
text of the mail message. This incorrect behavior
caused mail loop detection schemes that counted Received
By headers (including UCX's mail loop detection scheme)
to function improperly.
Caveat for V3.1:
Before UCX V3.2, a mail bounced by UCX SMTP because the
maximum number of hops was exceeded (i.e., due to having
too many Received By headers) was bounced with the
following failure text:
---- Transcript of session follows ----
%NONAME-E-NOMSG, Message number 030ADB32
UCX V3.2 will contain the correct failure text:
---- Transcript of session follows ----
%UCX-E-SMTP_EXCMAXHOP, Maximum number of hops exceeded.
Mail loop suspected
ECO D 23-Aug-1994 VAX and AXP
Images:
UCX$SMTP_MAILSHR.EXE UCX V3.1-32D
UCX$SMTP_RECEIVER.EXE UCX V3.1-32D
UCX$SMTP_SYMBIONT.EXE UCX V3.1-32D
UCX$SMTP_PARSESHR_TV.EXE UCX V3.1-32D
UCX$UUENCODE.EXE UCX V3.1-32D
UCX$UUDECODE.EXE UCX V3.1-32D
1. UCX SMTP would sometimes look inside a quoted local
part of an address when parsing it. It would mistakenly
attempt to parse the quoted local part as an RFC 822
address and if it found a '%', would think that
it found a case of user%host@someplace.xyz_corp.com.
The result was that the address was was bounced.
ECO 5 Updates:
--------------
ECO E 30-Sep-1994 VAX and AXP
Images:
UCX$SMTP_MAILSHR.EXE UCX V3.1-32E
UCX$SMTP_RECEIVER.EXE UCX V3.1-32E
UCX$SMTP_SYMBIONT.EXE UCX V3.1-32E
UCX$SMTP_PARSESHR_TV.EXE UCX V3.1-32E
UCX$UUENCODE.EXE UCX V3.1-32E
UCX$UUDECODE.EXE UCX V3.1-32E
1. The UCX SMTP symbiont would ACCVIO if the number of
lines of text in the RFC header block was greater
than 100 *or* if the number of bytes in the RFC
header block was greater than 8192. This may occur
when mailing lists were expanded in the To: RFC header
line and not truncated by the sender.
2. UCX SMTP would sometimes become confused when it
encountered an address that contained special
characters like '<' or '>' inside a comment string.
This could cause an ACCVIO or could make a mail
message appear to be from an incorrect address.
For example:
""
3. If a user forwarded his mail via SMTP on a local
system, he would not be able to use the VMSmail
From: line to reply to a non-SMTP mailer. If the
non-SMTP transport from which the mail came was
DECnet, the From line would be enclosed in double
quotes. If the non-SMTP transport was MTS, the From:
line would be enclosed in double quotes and would also
contain backslashes preceding the inner double quotes
in the address.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 LPD Facility
----------------------------------------------------------------------------
ECO 1 Updates:
--------------
ECO A 9-Jun-1994 VAX/AXP
Images:
UCX$LPD_SHR.EXE UCX V3.1-32A
UCX$LPD_SMB.EXE UCX V3.1-32A
UCX$LPD_RCV.EXE UCX V3.1-32A
UCX$LPQ.EXE UCX V3.1-32A
UCX$LPRM.EXE UCX V3.1-32A
UCX$LPRSETUP.EXE UCX V3.1-32A
UCX$TELNETSYM.EXE UCX V3.1-32A
1. If the SMTP transport was not present and the LPD
symbiont tried to send mail notification, the
symbiont (i.e., the UCX$LPD_QUEUE) would stop.
2. The LPD symbiont would hang if a job was pending
in a stopped LPD queue and the queue was restarted.
3. For outbound print jobs, UCX LPD had no "retry"
capability. If the LPD print server did not
respond or if the connection went down, the job
would become "retained on error" and the LPD queue
would stop.
4. There are two ways to indicate a PostScript[R] file.
Standard LPD uses the 'o' card and Digital's LPD
Printserver Extensions (hereafter referred to as
the "PS extensions") use the 'Dpostscript' card.
It was not possible to configure LPD to use the
standard LPD procedure rather than the equivalent PS
extensions procedure where functional overlap existed.
5. Adding printers to printcap would cause the name of
earlier printer entries to bleed over into the names
of later ones if the length of the earlier printer names
was greater than the later ones.
6. When printing to a U*ix system with the
PRINT/PARAM=PRINTER="printer-name" command, the case
of the printer name was not being preserved. This
required a printer synonym (in all uppercase) for each
destination printer on the target U*ix system.
7. Performing a STOP/QUEUE/RESET on an LPD queue which
was currently processing a job would cause the symbiont
to exit abnormally.
8. The root always needed a proxy account regardless of
whether the application proxy was on or off.
9. For inbound jobs, if remote host from the 'H' control
card was not known, the job would end up retained on
error in the UCX$LPD_QUEUE with a "record not found"
error. This would happen regardless of the setting of
the LPD service's application proxy flag.
ECO 4 Updates:
--------------
ECO B 15-Sep-1994 AXP and VAX
Images:
UCX$TELNETSYM.EXE UCX V3.1-32B
1. The Telnet print symbiont would cause Form Feeds to
appear at the beginning of each job rather than at the
end. This might cause the waste of special print forms
for some applications.
2. There was no way to suppress inter-job form feeds entirely.
3. There was no way to stop the Telnet print symbiont from
acting as a "true" Telnet sender (i.e., no way to stop it
from doubling IAC characters and from doing a Telnet
negotiation of binary mode for printing PASSALL files).
ECO 5 Updates:
--------------
ECO C 30-Sep-1994 AXP and VAX
Images:
UCX$LPD_SHR.EXE UCX V3.1-32C
UCX$LPD_SMB.EXE UCX V3.1-32C
UCX$LPD_RCV.EXE UCX V3.1-32C
UCX$LPQ.EXE UCX V3.1-32C
UCX$LPRM.EXE UCX V3.1-32C
UCX$LPRSETUP.EXE UCX V3.1-32C
UCX$TELNETSYM.EXE UCX V3.1-32C
1. When the remote LPD client sent the control file
before the data file(s), the job would sometimes
end up "retained on error" in the UCX$LPD_QUEUE
queue with a "file not found" error.
2. Outbound UCX LPD jobs sometimes fail with a "File locked
by another user" error.
3. UCX LPD proxy mapping does not find proxies when the
'/REMOTE_USER' switch has been used with a wildcard.
For example, the following proxy would not be spotted:
VMS User_name Type User_ID Group_ID Host_name
SOMEUSER CD * someplace.xyz.org
^
|
Wildcarded remote |
user ------->------->--+
4. There was no way to configure the Telnet symbiont to
drop the TCP/IP link immediately at the end of a job.
5. The sharing of Telnet symbiont logs among execution
queue threads made logs difficult to read and caused
contention for log files between threads.
6. Telnet symbiont diagnostics were insufficient for problem
diagnosis at customer sites.
7. A problem in FF suppression code occurred when the
logical UCX$TELNETSYM_SUPPRESS_FORMFEEDS was defined
at queue startup. The result was that the last line of
a job would be overprinted by the first line of next
job.
8. If the LPD receiver has a problem opening the LOG file
(SYS$SPECIFIC:[UCX_LPD]UCX$LPD_RCV_LOGFILE.LOG), it
sends diagnostics to the operator console even if the
logical to turn on LPD receiver diagnostics is not
defined. (LPD_RCV is the LPD receiver diagnostics
logical).
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 Management Control Program (UCP)
----------------------------------------------------------------------------
ECO 2 Updates:
--------------
ECO A 01-JUL-1994 AXP and VAX
Images:
UCX$UCP.EXE UCX V3.1-32A
1. A server list entered via the UCX 'SET CONFIG NAME /SERVER'
command was sorted in order of ascending internet address,
causing the bind resolver to use an incorrect ordering.
2. The UCX 'CONVERT/ULTRIX BIND' command did not allow the
creation of a reverse domain.
3. If the destination parameter to the 'SET MX' command could
not be found in a host lookup, then an MX record would
not be created and no warning or error would be issued.
4. a. Four items in the communication configuration
parameters were being ignored by the 'START COMM /INIT'
command.
b. The configuration of communication security lists
was not working.
c. 'SET CONFIGURATION COMMUNICATION /REMOTE=NOVIRTUAL'
did not work.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 RSH
----------------------------------------------------------------------------
ECO 4 Updates:
--------------
ECO A 07-Jun-1994 AXP and VAX
Images:
UCX$RSH.EXE
1. Quotation characters were unconditionally removed from
the RSH command line.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 PWIP Driver and ACP
----------------------------------------------------------------------------
ECO 2 Updates:
--------------
ECO A 01-Jul-1994 AXP and VAX
Images:
UCX$PWIPACP.EXE UCX V3.1-32A
UCX$PWIPDRIVER.EXE UCX V3.1-32A
UCX$PWIPSHUT.EXE UCX V3.1-32A
1. Two ACCVIOs could occur during PWIP shutdown. The
first was caused by a null ucxucb pdcb field and
the second was caused by a null pdcb pointer passed
in a call to dwn_call_down. Both of these are valid
situations and should not cause access violations.
ECO 3 Updates:
--------------
ECO B 18-Jul-1994 AXP and VAX
Images:
UCX$PWIPACP.EXE UCX V3.1-32B
UCX$PWIPDRIVER.EXE UCX V3.1-32B
UCX$PWIPSHUT.EXE UCX V3.1-32B
1. The PWIP ACP log we misnamed. The PWIP ACP log file
name has been changed from PWIPACP_nodename.LOG to
UCX$PWIPACP_nodename.LOG to make it more consistent
with UCX file naming conventions.
2. PWIP ACP log file records were lost when a system
crashed. PWIP ACP file logic has been changed so
that records are flushed to disk after every write.
3. The OpenVMS AXP PWIP ACP log file could not be read while
the ACP is active. The PWIP ACP file logic has been
changed so that the log file is opened "shr=get".
4. Crash dump analysis was difficult. Logic was added
to zero PDCBs upon allocation and to zero PDCB flinks
and blinks upon removal from queues. Additional
counters were added to the UCX$SDA (SDA backed)
routine displays.
5. An ACCVIO might occur during processing of the PCB
during Build_CONN_ID processing. Build_CONN_ID was
modified to verify that the UCX version of the socket
still exists and, within that socket, the address of
the pcb before further processing.
6. Work queue analysis was difficult. A DEBUG check of
PDCB work queue status on close_dev has been added.
If the PDCB flink or blink is non-NULL, the system will
now crash.
7. Erroneous ACP and driver state machine operation leading
to incorrect routine calls, improper BG device interaction,
UCX interaction failures, a deallocation race condition
leading to intermittent ACCVIOs and potentially other
errors occurred.
o Unavailable data on return from UNITDATA request leading to Path-
works client failure. Properly setup the SRC_length and SRC_offset
fields of the unitdata structure during pwip_alloc_udata_ind rou-
tine execution.
8. The data returned from a UNITDATA request leading to
Pathworks client failure was not complete. The SRC_length
and SRC_offset fields of the unitdata structure are now
set up correctly during the pwip_alloc_udata_ind routine
execution.
ECO 4 Updates:
--------------
ECO C 05-Aug-1994 AXP and VAX
Images:
UCX$PWIPACP.EXE UCX V3.1-32C
UCX$PWIPDRIVER.EXE UCX V3.1-32C
UCX$PWIPSHUT.EXE UCX V3.1-32C
UCX$SDA.EXE UCX V3.1-32C
1. The PWIPdriver shutdown procedure did not function
correctly. It left the driver in an undefined
state which might cause ACCVIOs, transport user
bugchecks and/or an inability to restart.
2. The OpenVMS AXP version of PWIPdriver corrupted the
high order word of a longword field in the pdcb
which contained the channel number (normally a word
field) when passing information between the ACP and the
driver.
3. Some of the UCX PWIP SDA backed displays have been
upgraded.
ECO D 22-Aug-1994 AXP/VAX
Images:
UCX$PWIPACP.EXE UCX V3.1-32D
UCX$PWIPDRIVER.EXE UCX V3.1-32D
UCX$PWIPSHUT.EXE UCX V3.1-32D
UCX$SDA.EXE UCX V3.1-32D
1. Added a SyncState macro to ensure that the interface
state is synchronized between the transport user and
the transport provider before shutdown processing
begins for each TCP non-listener connection. There
was a remote possibility that PWIP would respond
inappropriately at shutdown causing the transport
user to crash the system.
2. The disconReq_ast routine in the PWIPacp_Ucx.C
module did not pass the status to the driver
correctly when an error occurred.
3. The pwip_check_disconnect routine in the
PWIPdriver_Supp.C module sometimes treated errors
as special case. It now only sends up a T_DISCON_IND.
4. Missing characters in the PWIPDRIVER_ACK.C. module of
the Build_CONN_IND routine may cause system crashes.
5. Conditionally compiled debug statements were added to
various routines to facilitate debugging.
6. Upgraded the build procedure:
a. Created and populated VMS platform/version-specific
system-wide build locations for the PWIP SDK files
provided by Pathworks:
> Build1$:[Plat_v.Vms_v55.PWIPSDK]
> Build1$:[Plat_a.Vms_v15.PWIPSDK]
> Build1$:[Plat_a.Vms_v61.PWIPSDK]
b. The PWIP.COM build procedure has been modified to
correctly access the proper PWIP SDK files, to
allow for ECO builds, to access the standard
system files, and to cease creation of dummy
OpenVMS AXP files.
c. The OpenVMS VAX portion of the Bliss DriverDef
file was modified to include missing macros and
to replace the VMS$RESD$ references with SYS$LIBRARY.
d. The Macro2Hfile.COM procedure has been modified to
proper deal with Macro-32 '.IF' directives, thus
removing the need to redefine certain symbols in
other files.
e. Reworked various files to accurately redefine certain
symbols thus avoiding DECC redefinition warnings and
the resultant Library and Linker warnings at compile
time.
7. StdCloseCnt and nonstdCloseCnt have been removed from
the UCX PWIP SDA backed displays since they no longer
exist.
ECO E 16-Sep-1994 VAX and AXP
Images:
UCX$PWIPACP.EXE UCX V3.1-32E
UCX$PWIPDRIVER.EXE UCX V3.1-32E
UCX$PWIPSHUT.EXE UCX V3.1-32E
UCX$SDA.EXE UCX V3.1-32E
Problems, solutions and/or enhancements:
1. On rare occasions, when PWIP Mbuf resource or session
limits are exceeded and the transport user decides to
abruptly terminate multiple sessions, the PWIPdriver
work queue may be corrupted leading to an ACCVIO and
system crash.
2. PWIPdriver startup and shutdown messages are now posted
to OPCOM.
3. PWIPdriver now dynamically recalculates Mbuf resource /
session limits whenever they are exceeded.
4. PWIPdriver now writes a message to OPCOM whenever
Mbuf resource / session limits are depleted and/or
replenished.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 SNMP_ AGENT
----------------------------------------------------------------------------
ECO 4 Updates:
--------------
ECO A 25-Aug-1994 VAX and AXP
Images:
UCX$SNMP_AGENT.EXE UCX V3.1-32A
1. ACCVIOs may occur when a getnext function traverses
the Address Translation table (AT). ACCVIOs may also
occur when DEBUG is enabled and an OID is printed.
2. The SNMP Agent reports an IPIOCTLERR - failure to read
IP information due to invalid buffer length.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 NFS Server
----------------------------------------------------------------------------
ECO 4 Updates:
--------------
ECO A 31-May-1994 VAX and AXP
Images:
UCX$SERVER_NFS.EXE UCX V3.1-32A
1. The hostname is being handled improperly in the
authentication portion of the NFS request. The
result is either a crash (of the NFS server) or a
loop, depending upon the request which is being made.
2. The NFS server improperly handles the UID and GID in the
NFS request under certain circumstances.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 CFS_SHR.EXE images
----------------------------------------------------------------------------
ECO 5 Updates:
--------------
ECO A 20-Jul-1994 AXP and VAX
Images:
UCX$CFS_SHR.EXE UCX V3.1-32A
1. Large files appeared to have corruption at the end.
2. SS$_INVACL was being encountered when processing attributes.
3. File deletion required the name to end in ".".
4. Purge code did not work correctly. An error in RVN
determination was discovered.
5. A system crash may occur if the client changes
the directory cookie to a value between 2 and 65535.
6. Directory ACLs are not propagated as expected.
7. Internal BFS event monitoring code fails to send a
thread exit event.
8. VFC print files are not processed properly.
9. The SVTX (``sticky'') bit in a directory's protection
mask indicates that the contents can only be deleted
by the owner or root. This was being ignored.
ECO B 02-Sep-1994 AXP and VAX
Images:
UCX$CFS_SHR.EXE UCX V3.1-32B
1. Several problems existed in CFS bitmap management routines
which produced a series of errors before the user's actual
problem could be addressed.
The problems encountered were:
a. Hangs were caused by problems in the AXP LIB$FFC and
LIB$FFS library routines. The NFS process would hang
in EXEC mode in RMS rundown at AST state. This would
prevent RMS from properly running down, making the
problem appear to be caused by RMS.
b. Errors in bitmap management occurred.
c. File system crashes occurred during the crossing
of bitmap boundaries. The error in the logic was
causing bits off the end of one bitmap to be manipulated
when they should have been manipulated in the NEXT bitmap.
This problem also caused corruption if a buffer or
data structure happened to be located after a bitmap
buffer in the virtual address space.
d. Bitmap initialization failed to mark a buffer as modified
which caused the cache to discard it. The last known
content of the bitmap area was a series of 128 deleted
cells. This was the CGIO error.
2. PC clients (several implementations) specify a zero size
on directory creation. This could cause an invalid
directory which not allow creation of files or subdirectories.
3. If ADD EXPORT was done with /OPTIONS=PURGE_VERSIONS, the
presence of a file with null name and extension (e.g., .;1)
makes the rest of the files in the directory invisible to
the ls command.
----------------------------------------------------------------------------
Fixes for DEC TCP/IP Services V3.1 DNFC Driver (Note: Not supported in V3.1)
----------------------------------------------------------------------------
ECO 1 Updates:
--------------
ECO A 26-May-1994 VAX and AXP
Images:
UCX$DNFCDRIVER.EXE UCX V3.1-32A
1. The driver would not load on OpenVMS AXP systems.
2. In very rare cases, the client would hang for no
apparent reason.
3. Empty ACLs are reported with SS$_NORMAL instead of
the expected SS$_ACLEMPTY return.
4. Privilege violation returned by SET FILE /ENTER.
5. The MOUNT /BUFFER=(READ=x, WRITE=y) qualifier is being ignored.
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.
REFERENCES:
PostScript is a registered trademark of Adobe Systems Incorporated.
UNIX is a registered trademark licensed exclusively by X/Open Company Ltd.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
ucxeco5-031.README
ucxeco5-031.CHKSUM
ucxeco5-031.a-dcx_axpexe
ucxeco5-031.a-dcx_vaxexe
|
