|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: system PRIVILEGED account (root
nfsserver.support.compaq.com)Date: Sat Jul 07 2001 - 07:58:39 CDT
*******************************************************************************
* *
* This is an update to an existing patch... *
* *
* Online links can be found at *
* http://ftp.support.compaq.com/patches/public/vms/axp/v7.1/tcpip/5.0a/dec-axpvms-tcpip_eco-v0500-113-4.README
*******************************************************************************
TITLE: Compaq TCP/IP TCPIPALP_E02A50 TCP/IP for OpenVMS V5.0A ECO Summary
New Kit Date : 08-JUN-2001
Modification Date: 04-JUL-2001
Modification Type: Internet Links Updated
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
For OpenVMS savesets, the name of the compressed saveset
file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
saveset is copied to your system, expand the compressed
saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
For PCSI files, once the PCSI file is copied to your system,
rename the PCSI file to kitname-dcx_axpexe.pcsi, then it can
be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 2000, 2001. All rights reserved.
PRODUCT: Compaq TCP/IP Services for OpenVMS
OP/SYS: OpenVMS Alpha
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: TCPIPALP_E03A50
DEC-AXPVMS-TCPIP_ECO-V0500-113-4.PCSI
ECO Kits Superseded by This ECO Kit: TCPIPALP_E02A50
ECO Kit Approximate Size: 46,400 Blocks
Kit Applies To: Compaq TCP/IP Services for OpenVMS V5.0A
OpenVMS Alpha V7.1, V7.1-1H1, V7.1-1H2,
V7.1-2, V7.2, V7.2-1, V7.2-1H1
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Information Not Available
Installation Rating: INSTALL_UNKNOWN
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for TCP/IP V5.0A on OpenVMS Alpha V7.1 through
V7.2-1H1. This kit addresses the following problems.
Release Notes for COMPAQ TCP/IP Services for OpenVMS V5.0A
Update ECO 3
DISCLAIMER
COMPAQ makes no claims regarding the use or performance of these
software ECOs. COMPAQ accepts no responsibility for any incurred
expenses, losses, or problems related to the installation and use
of this software.
COMPAQ provides no warranties either expressed or implied in law,
including IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE.
In no event shall COMPAQ have any liability for damages as
a result of the performance, use, or operation of this software.
The customer shall have the sole responsibility for adequate
protection and back-up of data used in conjunction with this
update kit. ECOs in this kit are cumulative. All previous updates
for Version 5.0A are included in this kit.
-------------------------------------------------------------------------------
POSSIBLE INSTALL PROBLEMS:
-------------------------------------------------------------------------------
There is a bug in the PCSI utility that ships in the following
kits that will cause the install to fail:
o DEC AXPVMS VMS V7.1-2 (OpenVMS Alpha V7.1-2)
o DEC AXPVMS VMS V7.2 (OpenVMS Alpha V7.2)
o DEC VAXVMS VMS V7.2 (OpenVMS VAX V7.2)
o DEC AXPVMS VMS62TO71U2_PCSI V1.0 (PCSI ECO kit for
OpenVMS Alpha V6.2 through V7.1-2)
o DEC VAXVMS VMS62TO71_PCSI V1.0 (PCSI ECO kit for
OpenVMS VAX V6.2 through V7.1)
The PCSI utilities in the kits listed above were all built from
the same source code. They all identify themselves in the output
from the PRODUCT SHOW UTILITY command as:
"POLYCENTER Software Installation utility version: V7.2-100".
Contact your local Customer Support Center for PCSI upgrades.
-------------------------------------------------------------------------------
PREVIOUSLY UNDOCUMENTED BEHAVIOR:
-------------------------------------------------------------------------------
---------------------------------------------------------------
1: PTR 70-5-1299 Retry and error ignore for MIB browser
---------------------------------------------------------------
The DIGITAL TCP/IP Services for OpenVMS Management manual,
Order Number: AA-LU50K-TE, Chapter 11 Configuring SNMP,
Table 11-4 Flags for the snmp_request Command will be updated
with the following new flags:
-i max_ignores: The number of times snmp_request listens for a reply packet
to a request if it receives an invalid packet (invalid packet
id, version, SNMP version/command combination). Value should
be positive; specifying a negative value results in internal
conversion to an unsigned positive; specifying 0 is the same
as omitting this flag, in which case errors are not ignored.
-r max_retries: The number of times snmp_request resends a request packet if it
times out before receiving a reply. Value should
be positive; specifying a negative value results in internal
conversion to an unsigned positive; specifying 0 is the same
as omitting this flag, in which case no retries are tried.
-s sleep_interval: Seconds between iterations of sending a request (for -r)
and listening for a reply (for -i). Default is 1 second.
Ignored unless -r, -i, or both are also specified.
Notes:
- The -s flag is not the same as -w, which is used to adjust timeout
interval for the internal select() call. -s may be needed in
cases where there is a need to enforce a wait between resend, as
when a server agent which is in the process of starting up.
- After a timeout and resend, if a reply packet is received the resend
counter is reset; after another timeout, max_retries request packets
will be sent.
- The same is true for max_ignores. After a bad reply is received, if
a valid reply packet is received, the internal ignore counter is
reset to max_ignores.
- The -s value may be required in cases where a server is in some
transient state, e.g., in the process of coming up.
- Following receipt of an invalid packet, a timeout may occur. In this
case the packet will be resent, the resend counter will be decremented,
and the ignore counter will be reset to max_ignores.
- -i, -r, and -s apply to individual queries. If the -l or -t flags are
also used, the values for -i, -r, and -s are applied afresh to each
iteration for the -l or -t.
- The -i flag does not cause snmp_request to automatically increment input
OID and continue querying a server after an SNMP general error has been
received. For example, on a mibwalk (result of using -t or -l flag)
if a faulty server may with this kind of error even though the end
of MIB view has not been reached. It is still necessary to manually
increment the input OID to skip the error to continue with the mibwalk.
The following examples will be added to 11.6.4 Command Examples
for snmp_request:
Add these 2 bullets at the beginning of the section:
- To define the command snmp_request, you can execute the command:
$ SYS$STARTUP:TCPIP$DEFINE_COMMANDS.
- In all examples, output may be edited to fit the 80 column format, with
continuation indicated by a "\" at the end of a line
Add the following examples:
9. To get online UNIX style usage information, enter the command without
parameters:
$ snmp_request
Usage: $ snmp_request = \
"$ucxaxp$dkd400:[tcpip_t51_bl9z.][a70.snmp.exe]tcpip$snmp_request.exe"
$ snmp_request agent community request_type [flags] \
[set request parameters]
or
$ mcr \
ucxaxp$dkd400:[tcpip_t51_bl9z.][a70.snmp.exe]tcpip$snmp_request.exe ...
request_type: get|getnext|getbulk|set
flags: [-v version] [-p port] [-l] [-t] [-d]
[-n non_repeaters] [-m max_repetitions]
[-w wait_seconds_max] [-i max_ignores]
[-r max_retries] [-s sleep_interval]
set request parameters: variable [type value]
10. The server is not up when the request is sent.
It comes up, starts responding, and then goes down again.
$ snmp_request moxie.zko.dec.com public getnext -r 3 -l -s 5 1.3
No reply; resending request...
1.3.6.1.2.1.1.1.0 = moxie.zko.dec.com VAX 6000-410 OpenVMS V7.1 \
Compaq TCP/IP Services for OpenVMS
1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.36.2.15.22.1
1.3.6.1.2.1.1.3.0 = 198 = 0 d 0:0:1
1.3.6.1.2.1.1.4.0 = Sam Spade
1.3.6.1.2.1.1.5.0 = moxie.zko.dec.com
1.3.6.1.2.1.1.6.0 = ZKO
1.3.6.1.2.1.1.7.0 = 72
No reply; resending request...
No reply; resending request...
No reply; resending request...
No reply; resend limit reached. Exiting.
11. The server is not up when the request is sent.
Then the server comes up, but is not fully initialized when the second
request packet is sent:
$ snmp_request moxie.zko.dec.com public getnext -r 3 1.3
No reply; retrying...
- no such name - returned for variable 1
12. This example is identical to #3, except that the -s 5 causes a
delay in the sending of the second request packet, giving the server time
to fully initialize itself:
$ snmp_request moxie.zko.dec.com public getnext -r 3 -s 5 1.3
No reply; retrying...
1.3.6.1.2.1.1.1.0 = moxie.zko.dec.com VAX 6000-410 OpenVMS V7.1 COMPAQ TCP/IP
Services for OpenVMS
13. The following is happening:
- A bad reply packet is received
- A timeout causes a new request packet to be sent
- A second bad reply packet is received
- Another timeout causes a new request packet to be sent
- A third bad reply packet is received
- The max_tries limit of 2 has been reached, so snmp_request exits.
$ snmp_request moxie.zko.dec.com public getnext -i 3 -r 2 1.3
Unexpected reply; waiting again...
No reply; resending request...
Unexpected reply; waiting again...
No reply; resending request...
Unexpected reply; waiting again...
No reply; resend limit reached. Exiting.
14. This example is identical to #5 except that max_retries
is greater than max_ignores. Only two extra request packets are sent
before the max_ignores limit is reached:
$ snmp_request moxie.zko.dec.com public getnext -i 2 -r 3 1.3
Unexpected reply; waiting again...
No reply; resending request...
Unexpected reply; waiting again...
No reply; resending request...
Unexpected reply; ignore limit reached. Exiting.
15. This example is identical to #5, except that all invalid packets are
received before any timeouts; therefore no resends are tried:
$ snmp_request moxie.zko.dec.com public getnext -i 3 -r 2 1.3
Unexpected reply; waiting again...
Unexpected reply; waiting again...
Unexpected reply; waiting again...
Unexpected reply; ignore limit reached. Exiting.
----------------------------------------------------------------
2: PTR 70-5-1348 LPD print symbiont inserts LF characters
----------------------------------------------------------------
The following two logicals have been added for the LPD print
symbiont to fix the following problem:
LPD print symbiont inserts LF character after setup
module.
Defining the logical TCPIP$LPD_SETUP_NOLF will suppress
the LF characters on a per-system basis.
Defining the logical TCPIP$LPD_<queue>_SETUP_NOLF will
suppress the LF characters on a per-queue basis.
-----------------------------------------------------------------
3: PTR 70-5-1642 Windows NT NFS server can hang w/o /NOADF
-----------------------------------------------------------------
With some Windows NT and Windows 2000 NFS Servers (bundled with
Compaq TaskSmart [WNT 2000 Disk Access]), the OpenVMS NFS
client will hang attempting to reconstruct a file using it's
companion ADF. The Windows NFS server refuses to respond if
the ADF filename is .$ADF$000000. Since this name is a legal
filename, the long term solution is to ask Microsoft to fix their
NFS server. The short term or interim solution is to mount the
device with either the /RETRIES=<small integer> option or the
/NOADF option.
Please note that the default behavior beginning at TCP/IP V5.1
has been changed to /RETRIES=4 instead of /RETRIES=0 (forever).
-----------------------------------------------------------------
4: PTR 30-5-313 RCP copy changes the file attributes
-----------------------------------------------------------------
"$ COPY/RCP" on a binary file changes the file attributes
from fixed length to STREAM LF and corrupts the file.
To resolve this problem, RCP will now treat VMS fixed-length (FIX)
and undefined (UDF) format files as binary and copy them verbatim
without doing the implicit conversion to Stream_LF. Note however
that RCP will NOT preserve file attributes on the target file
(which will still be created as Stream_LF). To fix this is beyond
the scope of an ECO and may not be possible without incompatibly
breaking the RCP protocol. File attributes on the target will have
to manually be corrected by the user.
Lest some customers have come to depend on the original behavior of
RCP, that behavior can be restored by setting the logical
TCPIP$RCP_SEND_FIX_FORMAT_AS_ASCII to "1", "True", or "Yes".
However, if this logical is set to a numeric value that exactly
matches the fixed-length file's record size, that file will not be
converted to Stream_LF, but will be sent as binary.
Note also, the TCPIP$RCP_SEND_FIX_FORMAT_AS_ASCII logical name will
superceed the use of the UCX$RCP_SEND_FIX_FORMAT_AS_ASCII logical
name. Both are accepted logicals.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A ARP Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 19-APR-2000 Alpha and VAX
Images:
TCPIP$ARP.EXE V5.0A-1A
TCPIP$NETSTAT.EXE V5.0A-1A
TCPIP$GATED.EXE V5.0A-1B
TCPIP$UCP.EXE V5.0A-1F
Problem:
System can crash executing TCPIP> netstat -rn
Solution:
The NLIST library was modified necessitating the relink
of ARP, NETSTAT, GATED and UCP.
ECO B 23-JUN-2000 Alpha and VAX
Images:
TCPIP$UCP.EXE V5.0A-1G
TCPIP$NETSTAT.EXE V5.0A-1B
TCPIP$PING.EXE V5.0A-1A
TCPIP$IFCONFIG.EXE V5.0A-1A
TCPIP$SYSCONFIG.EXE V5.0A-1A
TCPIP$ESNMP_SERVER.EXE V5.0A-1I
TCPIP$HR_MIB.EXE V5.0A-1I
TCPIP$OS_MIBS.EXE V5.0A-1I
TCPIP$ARP.EXE V5.0A-1B
TCPIP$TRACEROUTE.EXE V5.0A-1A
Problem:
tcpip show route fails with INSVMEM when route database is large
Solution:
Backported fix from tcpip Version 5.1 that addresses this issue in
the unix_api library.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A BFS Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 24-MAR-2000 Alpha and VAX
Images:
TCPIP$CFS_SHR.EXE V5.0A-1A
TCPIP$MSG.EXE V5.0A-1C
Problem:
Message: cache_check detected corrupted LRU queue appears
on console after a mount from an nfs client hangs.
Solution:
Fixed miss-compare problem. Used STAT_CHE$W_CLUSTER_COUNT
instead of STAT_CHE$W_CLUSTER_LIMIT.
ECO B 18-MAR-2000 Alpha and VAX
Images:
TCPIP$CFS_SHR.EXE V5.0A-1B
Problem:
When UCX$CFS_MODUS_OPERANDI is set to 512, and a VMS NFS
client is being used, the NFS server sometimes reports
FCPREADERR ACCVIO ILLIOFUNC. This prevents the client from
accessing some files.
Solution:
Ported from 4.2.
Fixed handling of UCX$CFS_MODUS_OPERANDI 512 to not break the
communication of the VMS file's attributes between the VMS
NFS-Client and the VMS NFS-Server.
ECO C 3-MAY-2000 Alpha and Vax
Images:
TCPIP$CFS_SHR.EXE V5.0A-1C
Problem:
Problem wih BFS not returning an error status for bad
arguments. I.E. The synch status.
Solution:
Fixed bfs$$synch-alpha.m64 to save R0 from $$STARTUP.
ECO D 12-JUN-2000 Alpha and VAX
Images:
TCPIP$CFS_SHR.EXE V5.0A-1D
Problem:
Backup errors on NFS due to a failure to allocate
space for access control lists (ACL).
Solution:
Allocate space for the ACL and only return an error if unable to
allocate it due to lack of space available in the system.
ECO 3 updates
--------------
ECO E 6-OCT-2000 Alpha and VAX
Images:
TCPIP$CFS_SHR.EXE V5.0A-1E
Problem:
When copying a file from a NFS client to the NFS Server the server
stops sending data and the thread usage then increases to the
maximum.
Solution:
Fixed NFS server locking problem.
ECO F 17-JAN-2001 Alpha and VAX
Images:
TCPIP$CFS_SHR.EXE V5.0A-1F
Problem:
NFS problem with file aliases where certain file aliases created
on the VMS side are only partly visable on Unix.
Solution:
Treat all file aliases to directories as directories when
MODUS_OPERANDI bit 16384 is set.
ECO G 30-MAR-2001 Alpha and VAX
Images:
TCPIP$CFS_SHR.EXE V5.0A-1G
Problem:
For file systems exported with /options=Name_Conversion,
any particularly long filename can map to the VMS file ".;"
which can be disconcerting and confusing.
Solution:
Properly detect when NonVMS-to-VMS name conversion fails and
report this as an appropriate error back to the client (e.g.
NAMETOOLONG). NonVMS filenames that cannot be converted into
a legal VMS ODS-2 filename can only be accommodated within a
Container File System.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A BIND_RESOLVER Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 18-Apr-2000 Alpha and VAX
Images:
TCPIP$BIND_SERVER.EXE V5.0A-1B
TCPIP$BIND_SERVER_CONTROL.EXE V5.0A-1B
Problem:
BIND 8.1.2 did not include dynamic update support for SRV records.
Solution:
Extract and merge the SRV support from BIND 8.2 into our current
sources.
ECO 3 updates
--------------
ECO B 6-NOV-2000 Alpha and VAX
Images:
TCPIP$BIND_SERVER.EXE V5.0A-1B
TCPIP$BIND_SERVER_XFER.EXE V5.0A-1B
TCPIP$NSUPDATE.EXE V5.0A-1B
Problem:
BIND_RESOLVER allocates too much stack, 32 Kb on Alpha
and 8 Kb on VAX.
Solution:
Modified res_init() and res_query() (another culprit) to use
NS_MAXDNAME instead of BUFSIZ when declaring the buf variable.
This will use 1k of stack instead of 32k (or 8k on vax).
ECO C 26-JAN-2001 Alpha and VAX
Images:
TCPIP$IPC_SHR.EXE V5.0A-1C
Problem:
The dynamic updates being sent by the load broker to a
Windows2000 DNS server were failing with an error similiar to:
unknown response: ans=0, auth=1, add=1, rcode=3
Solution:
Modify the check on the response packet from an SOA query to accept
packets that have an empty answer section, auth=1, and add=1.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A BIND_SERVER Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 06-Aug-1999 Alpha and VAX
Images:
TCPIP$BIND_SERVER.EXE V5.0A-1A
Problem:
The BIND server was reporting syntax errors when CIDR notation
was used in the configuration file (TCPIP$BIND.CONF).
Solution:
There were a couple of different reasons for this problem. The
first was that there were two successive calls being made to
ungetc(). This is an unsupported operation and led to
inappropriate behavior. To cure this, an f*() file positioning
function must be made in between calls to ungetc() in order to
clear the pushback buffer. The pushback buffer is where ungetc()
writes it char to. It does not get placed back to the actual file
buffer. The size of the pushback buffer for the DEC C RTL is 1,
and once it is full additional calls to ungetc() will fail. I
chose to use a call to fseek() that would basically just position
the file pointer to its current position (a no-op besides clearing
the buffer).
The other problem was that due to the parser logic behind
determining whether a slash ('/') was part of a comment or part of
a CIDR notated IP address, the file positioning pointer became a
char ahead of where it should have been. This was after a series
of getc() and ungetc() calls. This problem was solved by doing an
fgetpos()/fsetpos() combo to reset the file position indicator.
There was also a bug discovered here where the code still does not
work if it is compiled with /NOOPTIMIZE on a VAX. This happens if
you compile for debug in our build environment (only VAX). Seeing
we do not ship /NOOPTIMIZED code, we will ignore this optimizer bug
and be sure to add a regression test item that will verify that
this continues to work as expected in the future. The bug could
not be reproduced with a simple test program, only in context of
the BIND code.
ECO B 18-MAR-2000 Alpha and VAX
Images:
TCPIP$BIND_SERVER.EXE V5.0A-1B
TCPIP$BIND_SERVER_CONTROL.EXE V5.0A-1B
TCPIP$BIND_SERVER_XFER.EXE V5.0A-1A
TCPIP$NSUPDATE.EXE V5.0A-1B
Problem:
BIND 8.1.2 did not include dynamic update support for SRV records.
Solution:
Extract and merge the SRV support from BIND 8.2 into our current
sources.
ECO 3 updates
--------------
ECO C 10-OCT-2000 Alpha and VAX
Images:
TCPIP$BIND_SERVER.EXE V5.0A-1C
TCPIP$BIND_SERVER_XFER.EXE V5.0A-1C
Problem:
The BIND database was not being updated once its version number
reached the VMS maximum of 32767.
Solution:
If a "rename" call for the database fails, we purge the previous
versions of the database, then rename the current version to have
version number 1.
ECO E 6-NOV-2000 Alpha and VAX
Images:
TCPIP$BIND_SERVER.EXE V5.0A-1E
TCPIP$BIND_SERVER_XFER.EXE V5.0A-1E
TCPIP$NSUPDATE.EXE V5.0A-1E
Problem:
BIND_RESOLVER allocates too much stack, 32 Kb on Alpha
and 8 Kb on VAX.
Solution:
Modified res_init() and res_query() (another culprit) to use
NS_MAXDNAME instead of BUFSIZ when declaring the buf variable.
This will use 1k of stack instead of 32k (or 8k on vax).
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A BIND_TOOLS Images
---------------------------------------------------------------------------
ECO 3 updates
--------------
ECO A 20-APR-2001 Alpha and VAX
Images:
TCPIP$ACCESS_SHR.EXE V5.0A-1C
Problem:
TCPIP> show host ACCVIOs in certain cases when
retrieving the BIND database.
Solution:
NSLOOKUP was modified to deal with large DNS messages.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A DHCP Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 28-MAR-2000 Alpha and VAX
Images:
TCPIP$DHCP_SERVER.EXE V5.0A-1A
Problem:
DHCP does not send the "Bootfile name" with the DHCP BootReply
packet if BootP is redirect to another system.
The DHCPCAP file does not support ":" and "\" characters in the
BootFile field.
Solution:
The DHCP server was modified so that if a TFTP server IP address
is configured, then the code just takes what it has in the
configured Bootfile name verbatim and returns that to the client.
ECO 3 updates
--------------
ECO B 5-DEC-2000 Alpha
Images:
TCPIP$DHCP_BPASCIITODBMOD.EXE V5.0A-1B
TCPIP$DHCP_BPISAMTOASCII.EXE V5.0A-1B
TCPIP$DHCP_DBDUMP.EXE V5.0A-1B
TCPIP$DHCP_DBMODIFY.EXE V5.0A-1B
TCPIP$DHCP_DBREGISTER.EXE V5.0A-1B
TCPIP$DHCP_DBSHOW.EXE V5.0A-1B
TCPIP$DHCP_GUI.EXE V5.0A-1B
TCPIP$DHCP_SERVER.EXE V5.0A-1B
TCPIP$DHCP_SHOWDBS.EXE V5.0A-1B
TCPIP$DHCP_SIGNAL.EXE V5.0A-1B
Problem:
DHCP Server 5.0A, NT client cannot get IP address, when
coming from another subnet.
Solution:
Backport the changes from the V5.1 code which correctly
puts the port number in network byte order.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A DNFS Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A 06-Jul-1999 Alpha and VAX
Images:
TCPIP$DNFSACP.EXE V5.0A-1A
Problem:
Beginning with VMS V7.2, running BACKUP on an NFS client
device results in "-SYSTEM-F-BADATTRIB, bad attribute
control list" errors.
Solution:
The client was doing an argument validation on the size of
the buffer provided to receive the ATR$C_ASCNAME
attribute. Prior to VMS V7.2, this was wrong, but had no
practical effect. In V7.2, BACKUP changes to support EFS
make the incorrect validation visibly harmful. The
solution is to eliminate the length validation on
ATR$C_ASCNAME.
ECO 3 updates
--------------
ECO B 1-AUG-2000 Alpha and VAX
Images:
TCPIP$DNFSACP.EXE V5.0A-1B
Problem:
The original problem under 70-5-1203 is a crash in UCX$DNFSACP due
to memory corruption. A diagnostic module was sent which then
hung the NFS client when it caught the udp_recv_ast touching
deallocated memory.
Also found a bug in cnfs-proxy where the zeroing of memory after
the username characters was modifing 1 too many bytes.
Solution:
Avoid freeing the TRANS block if there is still a receive
outstanding.
Changed the condition in the zeroing "for loop" from <= to < so
that only the allocated bytes are modified.
ECO C 28-SEP-2000 Alpha and VAX
Images:
TCPIP$DNFSACP.EXE V5.0A-1C
Problem:
Introduced regression with fix for 70-5-1340.
Regression is present in TCP/IP V5.0A and V5.1.
Solution:
Remove some lines of code that were missed when
70-5-1340 was fixed.
ECO D 19-OCT-2000 Alpha and VAX
Images:
TCPIP$DNFSACP.EXE V5.0A-1D
Problem:
Rename of files that the client provides with default ADFs
get deleted if the owner is not the one renaming.
Solution:
During a rename, avoid creating an ADF file for files that
already have default ADF.
ECO E 29-MAR-2001 Alpha and VAX
Images:
TCPIP$DNFSACP.EXE V5.0A-1E
Problem:
The NFS client does not send a set attribute to the server after
writing a file that is the same size or smaller, letting it default
to 512 bytes. Initial fix attempt caused a data corruption
regression.
Solution:
Send a setattr procedure to set the size after the re-write,
being careful not to confuse this situation with the one that
led to file corruption. Also, backported V5.1 change so the
NFS client now reports the correct allocated size instead of
the EOF mark.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A FTP_CLIENT Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 2-AUG-1999 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1A
TCPIP$FTP_CHILD.EXE V5.0A-1B
Problem:
SYSTEM-F-NOIOCHAN, with FTP and search list logical
Solution:
Implemented changes throughout FTP regarding the use of
of sys$parse() to mitigate implicit channel usage.
ECO A 9-SEP-1999 Alpha only
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1A
TCPIP$FTP_CHILD.EXE V5.0A-1B
Problem:
FTP client "get a.a.a.a" from Unix host fails with
-RMS-E-CRE, ACP file create failed
-SYSTEM-W-BADFILEVER, bad file version number
Problem occurs only with TCPIP V5 on Alpha VMS 7.2. On VAX, or
Alpha VMS V7.1, the transfer succeeds because "a.a.a.a" is
converted to "a_a_a.a;1" to make RMS happy.
Solution:
Moved all filename conversion operations into
FTP$COMMON_HFS_SUPPORT library where knowledge of ODS-2 vs. ODS-5
parsing conventions are known or can be discerned. Enhanced their
functionality to allow ODS-5 conversion of foreign filenames, and
to provide a backstop conversion back to ODS-2 when an attempt is
made to try creating an ODS-5 name on an ODS-2 volume. Both FTP
Client GET and FTP Server PUT operations were affected.
ECO A 4-JAN-2000 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1A
Problem:
The FTP 'mput' command does not search the several
equivalence names defined by a logical name correctly.
Solution:
This problem was partly caused by 70-5-839 fix to
eliminate channel leaks, in which several uses of
SYS$PARSE were changed to be syntax-checking only.
mput no longer passes the expanded result of its
SYS$PARSE down to wldcrd_put_process().
A similar problem with the recv and dir/out= commands,
and with $copy/ftp remote local were also corrected.
ECO A 5-APR-2000 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1A
TCPIP$FTP_CHILD.EXE V5.0A-1B
Problem:
FTP Client occasionally hangs in accept().
Solution:
Use select() to monitor both the data and control ports.
ECO 3 updates
--------------
ECO B 11-JUL-2000 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1B
Problem:
[1] FTP Client assumes that * is invalid for output filename.
This may not be true if Server is non-VMS.
[2] FTP send command ACCVIO's if globbing is off.
Solution:
[1] Allow the FTP Server to determine if special characters
are valid for the output filename if not VMS Plus mode.
[2] Unconditionally set command type.
ECO C 18-JUL-2000 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1C
Problem:
COPY/FTP (get) or FTP> GET client hangs when retrieving
a large file which already exists on the local system.
Solution:
Check if a socket already exists; if yes, then call
function CLOSE_SOCKET_AND_CHAN(data) to close it down.
ECO D 8-NOV-2000 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1D
Problem:
ACCVIO when using FTP/INPUT=<input file>.
Solution:
Modify the client to recognize both an exit statement and
EOF (the end of the /INPUT file).
ECO E 18-DEC-2000 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1E
Problem:
FTP client gives access violation when using stream_LF
input files; problem occurs after installation of ECO 1.
Solution:
ftp$$fgets() was modified to use fgets() to read files
and then parse them depending on the record format and
record attributes.
ECO F 25-APR-2001 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1F
TCPIP$FTP_CHILD.EXE V5.0A-1I
TCPIP$FTP_SERVER.EXE V5.0A-1I
TCPIP$MSG.EXE V5.0A-1D
Problem:
For file larger than 4 GB, the FTP Client incorrectly reports the
number of bytes transferred. The Kbytes/sec rate reported is also
incorrect.
Solution:
The bytes transferred count is now maintained using an extended
precision representation (64-bit long long on Alpha, two 32-bit
longword array on VAX). The Kbytes/sec rate is now calculated
using double floating-point precision.
Also took this opportunity to include an estimate of a
sequential or fixed-length file's byte length in the
"150 Opening data connection for..." message.
Unix servers do this and it gives a GUI FTP client something
to use for progress bars or %complete screen updates.
Note this size is not 100% accurate due to file conversion
that might occur for the transfer.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A FTP_SERVER Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 7-JAN-2000 Alpha and VAX
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1A
Problem:
FTP> del .; command does not works after UCX was upgraded
from 4.0 ECO 5 to UCX 4.2 ECO 3. Error is: "550 The file
specification must contain a name, type and version number
(even if wildcarded)."
Solution:
Modify FTP DELE command to relax this restriction to just
requiring a version number, in order to accommodate files
that consist of just a name, or just a type.
ECO B 14-JUN-1999 Alpha/VAX
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1B
Problem:
An issue with FTP server handling of APPEnd was discovered
during analysis/ testing of 70-5-840.
Solution:
Only set "rms_posted = TRUE" if the preceding RMS call returns
SS$_SUCCESS status in *both* appe_ascii() and similar code in
recv_ascii().
ECO B 14-JUN-1999 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1A
TCPIP$FTP_CHILD.EXE V5.0A-1B
Problem:
Many FTP commands unnecessarily consume VMS channels in both
client and server when a search-list logical is involved in
the operation. This eventually results in SYSTEM-F-NOIOCHAN
error. User must start a new FTP session to make further
progress.
Solution:
Fixed FTP (both client and server) to clean up channels
no longer needed after each command.
ECO B 1-SEP-1999 Alpha and VAX
Image:
TCPIP$FTP_SERVER.EXE V5.0A-1B
Problem:
V5.0 Ftp Child Process creating process owner of
asterisk (*).
Solution:
The FTP Server was fixed to behave like it did in UCX V4.
If the prospective user is known to VMS, the child process
will be owned by that user from inception. If the
prospective user is not known to VMS, the short-lived
child process will be owned by the FTP Server (parent)
process ([TCPIP$AUX,TCPIP$FTP] as configured in the
Service database) until it dies due to login failure.
ECO B 03-SEP-1999 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1A
TCPIP$FTP_CHILD.EXE V5.0A-1B
Problem:
[1] Put/Convert inserts extra LineFeeds (LF) when sending
certain VFC files. (70-5-954)
[2] FTP Client does not send STRU R files correctly in
ASCII mode. Regression from UCX V4.0 ECO stream.
(70-5-110)
Solution:
[1] Fixed FTP's conversion algorithm to perform a more
faithful conversion of VFC/PRN prefix/suffix code
combinations with a better mapping to FTP ASCII
records on the wire. This affected both the client
(Put/Convert) and the server (TCPIP$FTP_CONVERT_FILE
logical).
[2] Fixed FTP client to send proper <IAC><01> end-of-
record tag.
ECO B 10-Sep-1999 Alpha and VAX
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1B
Problem:
FTP 'sunique' (store unique) put operations could
overwrite an existing version of the specified file
if the target filename includes a version specification.
Solution:
Fixed the FTP server STOU operation to create a new
version for the file regardless of any specified version
or file transfer mode (ASCII, BINARY, VMS-Plus).
Also fixed instances where a filename parsing error
in the server's RETR, STOR, or STOU commands could
result in a corrupted 501 error message.
ECO B 9-SEP-1999 Alpha only
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1B
TCPIP$FTP_CLIENT.EXE V5.0A-1A
Problem:
FTP client "get a.a.a.a" from Unix host fails with
-RMS-E-CRE, ACP file create failed
-SYSTEM-W-BADFILEVER, bad file version number
Problem occurs only with TCPIP V5 on Alpha VMS 7.2. On VAX, or
Alpha VMS V7.1, the transfer succeeds because "a.a.a.a" is
converted to "a_a_a.a;1" to make RMS happy.
Solution:
Fixed FTP to deal with Alpha VMS V7.2 "enhancements" to sys$parse()
which is now happy to parse Extended File System (ODS-5) pathnames
even though the underlying volume specified in the pathname is
still ODS-2.
FTP now catches an attempt to use an ODS-5 filename on an ODS-2
volume, and performs the filename conversion it traditionally did
to make the name ODS-2 conformant.
FTP also now performs an ODS-5 filename conversion rather than a
more restrictive ODS-2 conversion when the underlying volume is
ODS-5. This generally results in a name much closer to the
original than ODS-2 allowed.
ECO B 15-Dec-1999 Alpha and VAX
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1B
Problem:
FTP> del .; command does not works after UCX was upgraded
from 4.0 ECO 5 to UCX 4.2 ECO 3. Error is: "550 The file
specification must contain a name, type and version number
(even if wildcarded)."
Solution:
Modify FTP DELE command to relax this restriction to just
requiring a version number, in order to accommodate files
that consist of just a name, or just a type.
ECO 3 updates
--------------
ECO C 31-JUL-2000 Alpha and VAX
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1C
Problem:
FTP (server) is producing "ls" output that is malformed --
i.e. two filenames which should be on separate lines are not
separated by \r\n but by \0\0 NUL characters.
Solution:
Replace faulty conditional expression and verify that each entry
is now properly appended with \r\n (carriage return - line feed).
ECO D 20-OCT-2000 Alpha and VAX
Images:
TCPIP$FTP_SERVER.EXE V5.0A-1D
Problem:
TCPIP$FTP server process opens the TCPIP$FTP_SERVER_ANNOUNCE
file for each incoming session, but fails to close it properly
resulting in the FILLM (file limit) quota becoming exhausted.
Solution:
Modify finish_anonymous_message() to call sys$disconnect() and
sys$close() with the correct pointers.
ECO E 27-NOV-2000 Alpha and VAX
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1E
Problem:
Using a DECnet node name in the path of the ftp 'get' command
fails with error message:
550-Unable to determine the file type for <uninitialized data>
Solution:
Initialize resultant_name prior to calling check_filetype()
if the sys$search() path in retr() was somehow avoided.
ECO F 16-FEB-2001 VAX ONLY
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1F
Problem:
Fix for 70-5-1308 caused client DIR command to loop in
server producing blank lines.
Solution:
Wrong source got submitted in which a macro was used
instead of a global, causing an address miscompare.
Replaced use of macro with proper global symbol.
ECO G 19-FEB-2001 Alpha and VAX
Images:
TCPIP$FTP_SERVER.EXE V5.0A-1G
Problem:
FTP Server ACCVIO'S because the reallocation of the session
table on the 129th simultaneous connection fails.
Solution:
Dynamically reallocate the session table.
Session table grows by MAX_SESSIONS.
ECO H 24-APR-2001 Alpha and VAX
Images:
TCPIP$FTP_CHILD.EXE V5.0A-1H
Problem:
FTP> DIR search-list-logical can encounter the server errors
"550 file not found" or "550 unsupported file structure level"
when the search-list-logical is composed of concealed members.
Problem only occurs when file details are requested from the
server, and not when just filenames are requested.
Solution:
Modified the FTP server to better detect the transition from
one concealed device entry to another within a search-list-
logical's SYS$SEARCH() results, so it has the proper device
open for obtaining the requested file details.
ECO I 25-APR-2001 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1F
TCPIP$FTP_CHILD.EXE V5.0A-1I
TCPIP$FTP_SERVER.EXE V5.0A-1I
TCPIP$MSG.EXE V5.0A-1D
Problem:
For file larger than 4 GB, the FTP Client incorrectly reports the
number of bytes transferred. The Kbytes/sec rate reported is also
incorrect.
Solution:
The bytes transferred count is now maintained using an extended
precision representation (64-bit long long on Alpha, two 32-bit
longword array on VAX). The Kbytes/sec rate is now calculated
using double floating-point precision.
Also took this opportunity to include an estimate of a
sequential or fixed-length file's byte length in the
"150 Opening data connection for..." message.
Unix servers do this and it gives a GUI FTP client something
to use for progress bars or %complete screen updates.
Note this size is not 100% accurate due to file conversion
that might occur for the transfer.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A GATED Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 24-Aug-1999 Alpha and VAX
Images:
TCPIP$GATED.EXE V5.0A-1A
Problem:
When OSPF is configured, GATED process goes away after
running a little while. TCPIP$GATED_OUTPUT.LOG doesn't
show ACCVIO but TCPIP$GATED.LOG shows odd big number or
garbage characters for loopback interface index number.
Solution:
Fix the loop in krt_ifread() that goes through interface
table. When loopback interface was being processed it allowed
to exit the loop with ifrl pointing to uninitialized
space in memory.
ECO B 19-APR-2000 Alpha and VAX
Images:
TCPIP$ARP.EXE V5.0A-1A
TCPIP$NETSTAT.EXE V5.0A-1A
TCPIP$GATED.EXE V5.0A-1B
TCPIP$UCP.EXE V5.0A-1F
Problem:
System can crash executing TCPIP> netstat -rn
Solution:
The NLIST library was modified necessitating the relink
of ARP, NETSTAT, GATED and UCP.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A IFCONFIG Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 16-JUN-2000 Alpha and VAX
Images:
TCPIP$UCP.EXE V5.0A-1G
TCPIP$NETSTAT.EXE V5.0A-1B
TCPIP$PING.EXE V5.0A-1A
TCPIP$IFCONFIG.EXE V5.0A-1A
TCPIP$SYSCONFIG.EXE V5.0A-1A
TCPIP$ESNMP_SERVER.EXE V5.0A-1I
TCPIP$HR_MIB.EXE V5.0A-1I
TCPIP$OS_MIBS.EXE V5.0A-1I
TCPIP$ARP.EXE V5.0A-1B
TCPIP$TRACEROUTE.EXE V5.0A-1A
Problem:
tcpip show route fails with INSVMEM when route database is large
Solution:
Backported fix from tcpip Version 5.1 that addresses this issue in
the unix_api library.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A INET Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 22-Dec-1999 Alpha only
Images:
TCPIP$INETDRIVER.EXE V5.0A-1A
Problem:
Random unexplained crashes with stack corruption.
The stack appears misaligned, and systems crash
with weird PC's.
Solution:
The SUSPEND code for Alpha left the stack too low
by 12 bytes, hence also misaligned. Eventual
returns out of the thread would return to the AST
dispatcher which would attempt an REI instruction
with an 'off' SP. The results are unpredictable,
but most often the loaded PC causes an access
violation.
ECO B 29-Dec-1999 Alpha only
Images:
TCPIP$INETDRIVER.EXE V5.0A-1B
Problem:
Non-quadword alignment set at thread initialization.
Alpha kernel stack is just under 8KB, and should be
larger.
Solution:
Add an unused longword at the top of the thread structure.
Increase the size of the allocated memory to 16KB.
ECO 3 updates
--------------
ECO C 2-OCT-2000 Alpha and VAX
Images:
TCPIP$INETDRIVER.EXE V5.0A-1C
Problem:
I/O cancel does not return the OpenVMS error SS$_CANCEL as
the TGV NETDRIVER does.
Solution:
Added a macro to all return code translations to check for a
valid Unix exit code and, in the absence of one, return the
OpenVMS error code.
ECO D 31-JAN-2001 Alpha and VAX
Images:
TCPIP$INETDRIVER.EXE V5.0A-1D
Problem:
The INETdriver can cause a PGFIPLHI crash in VMS EXE$CANCEL.
Solution:
Fixed the INETdriver to make sure the CCB is paged into
memory before returning to EXE$CANCEL.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A INSTALL Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 17-APR-2000 Alpha and VAX
Source:
TCPIP$CONFIG.COM
Problem:
When running TCPIP$CONFIG for the first time after upgrading from
UCX V4.*, the user is asked if they wish to convert their old
databases to the new format. This conversion may have failed with
the error:%EDT-F-INTERERR, Internal software error; contact a
Compaq support representative%DCL-W-SKPDAT, image data (records not
beginning with "$") ignored
Solution:
Add switch EDTI/EDT/NOCOMMAND to ensure no INI files are
interpreted when EDT starts.
ECO A 21-APR-2000 VAX and Alpha
Sources:
TCPIP$CLEANUP.COM V5.0-01
TCPIP$SHUTDOWN.COM V5.0-008
TCPIP$UCP_STARTUP.COM V6.0-003
Images:
UCX$RPCXDR_SHR.EXE V5.0A-1
UCX$ACCESS_SHR.EXE V5.0A-1
Problem:
TCPIP V5.0A does not deliver copies of UCX$ACCESS_SHR.EXE and
UCX$RPCXDR_SHR.EXE, required so that images linked under
UCX V4.2 can run.
Solution:
Change build and install files to deliver those files.
UCX$RPCXDR_SHR.EXE is a copy of TCPIP$RPCXDR_SHR.EXE (V5.0A-1)
and UCX$ACCESS_SHR.EXE is a copy of TCPIP$ACCESS_SHR.EXE
(V5.0A-1).
ECO A 1-MAY-2000 Alpha and VAX
Images:
TCPIP$ESNMP_SERVER.EXE V5.0A-1B
TCPIP$OS_MIBS.EXE V5.0A-1B
Problem:
Customer cannot send SNMPv1 trap to client.
Solution:
Backport configuration option for V5.1. Allows customer to set
up text configuration file to supplement information configured
through TCPIP$CONFIG.COM in standard configuration file
SYS$SYSTEM:TCPIP$CONFIGURATION.DAT.
Customer must do the following:
$ COPY TCPIP$SNMP_EXAMPLES:TCPIP$VMS_SNMP_CONF.DAT -
SYS$SYSDEVICE:[TCPIP$SNMP]*.*;
Follow the instructions in that file to set up SNMPv1 trap(s).
Note that settings from standard TCPIP$*.DAT config files supersede
those in TCPIP$VMS_SNMP_CONF.DAT.
ECO A 12-MAY-2000 Alpha and VAX
Sources:
TCPIP$VMS_SNMP_CONF.DAT V5.0-01
Images:
TCPIP$ESNMP_SERVER.EXE V5.0A-1B
TCPIP$OS_MIBS.EXE.EXE V5.0A-1B
Problem:
SNMPv2 traps are default; V1 format expected by some SNMP clients
(e.g., NT).
Solution:
Backport configuration option for V5.1 that allows customer
to set V1 as default trap type. With this option, traps
configured through TCPIP$CONFIG.COM will be V1 format.
Customer must edit SYS$SYSDEVICE:[TCPIP$SNMP]TCPIP$VMS_SNMP_CONF.DAT
to remove the leading # in the line to uncomment it:
#config tcpip$snmp_v1_trap_default
ECO B 16-JUN-2000 Alpha and VAX
Images:
TCPIP$TNDRIVER.EXE V5.0A-1I
TCPIP$TELNET.EXE V5.0A-1B
Problem:
reverse telnet hangs on read when created with /noidle
Solution:
A new /PERMANENT option was added to create_session, to
start a network connection upon device assignment and
disconnect after deassignment.
ECO C 20-JUN-2000 Alpha and VAX
Images:
TCPIP$VERSIONS.EXE V5.0A-1C
Problem:
Update the TCPIP version that gets displayed using
'TCPIP SHOW VERSION', to indicate ECO 1.
Solution:
Recompile and link the version module.
ECO 2 updates:
--------------
ECO D 29-DEC-2000 Alpha and VAX
Sources:
TCPIP$CONFIG.COM
Problem:
If in UCX$CONFIG or TCPIP$CONFIG you go into 1-"Core Environment"
and then 4-"Interfaces" and change the internet address to a
different subnet address, the question "Enter broadcast mask for
xxxx" shows the old "Broadcast Address" and does not default to
the new "Broadcast Address". This often means that customers end
up with the wrong "Broadcast Address". This problem also exists
with the network mask default.
Solution:
Make sure the default values for the network mask and broadcast
mask are recalculated after a new IP address is entered.
ECO E 12-JAN-2001 Alpha and VAX
Images:
TCPIP$VERSIONS.EXE V5.0A-1E
Problem:
Update the TCPIP version that gets displayed using
'TCPIP SHOW VERSION', to indicate ECO 2.
Solution:
Recompile and link the version module.
ECO 3 updates:
--------------
ECO F 4-MAY-2001 Alpha and VAX
Images:
TCPIP$VERSIONS.EXE V5.0A-1F
Problem:
Update the TCPIP version that gets displayed using
'TCPIP SHOW VERSION', to indicate ECO 3.
Solution:
Recompile and link the version module.
ECO G 21-MAY-2001 Alpha and VAX
Sources:
TCPIP$INET_STARTUP.COM V6.0-09B3
Problem:
Many logical name translations of TCPIP$DEVICE and BG0
while running the Apache test.
Solution:
Defined the logical with an underscore:
$ DEFINE/SYSTEM/EXE TCPIP$DEVICE _BG0:
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A IPC Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A 17-AUG-2000 Alpha and VAX
Images:
TCPIP$IPC_SHR.EXE V5.0A-1A
Problem:
We failed to provide a mechanism for an application's AST routine
to abort mainline execution of a select() call. Some applications
require quick response to both I/O events and other events
without the resource consumption associated with busy-waiting.
Solution:
We have added a new routine to be called by the C RTL upon
receiving a signal. This routine will abort a pending
select() operation, if any, and cause that call to return EINTR
in errno, as it would on many UNIX systems.
ECO 2 updates:
--------------
ECO B 11-JAN-2001 Alpha and VAX
Images:
TCPIP$IPC_SHR.EXE V5.0A-1B
Problem:
Original: The new aborting-select behavior, in conjunction with a C
RTL change to activate it, could break some existing applications.
Current: Due to a build problem, there was no visible entrypoint
for the SELECT_ABORT fix in TCPIP$IPC_SHR.EXE ECO A (V5.0A-1A).
One of the symptoms of this problem is very poor performance.
Solution:
Original: Older applications may assume that select() will not
return upon receipt of a signal. Therefore, we abort only if the
logical name TCPIP$SELECT_ABORT_ON_SIGNAL has been defined
requesting this behavior.
Current: Re-build the ipc component from the srclib phase.
ECO 3 updates
--------------
ECO C 26-JAN-2001 Alpha and VAX
Images:
TCPIP$IPC_SHR.EXE V5.0A-1C
Problem:
The dynamic updates being sent by the load broker to a
Windows2000 DNS server were failing with an error similiar to:
unknown response: ans=0, auth=1, add=1, rcode=3
Solution:
Modify the check on the response packet from an SOA query to accept
packets that have an empty answer section, auth=1, and add=1.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A LBROKER Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A 30-Jul-1999 Alpha and VAX
Images:
TCPIP$LBROKER.EXE V5.0A-1A
Problem:
'max-members', a configuration option in TCPIP$LBROKER.CONF was not
working when set to 1. It was erroneously returning A records for
all active members to the BIND server instead of 1.
Solution:
The logic was such that it was checking for maxmembercnt > 1
when itshould have been > 0 to allow the possibility of
returning only 1record. Simply needed to change the 1 to a
zero.
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A LPD5 Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 15-SEP-1999 Alpha and VAX
Images:
TCPIP$TELNETSYM.EXE V5.0A-1A
Problem:
TCPIP$TELNETSYM.EXE (Telnet Symbiont Process) crashes
with an access violation, %SYSTEM-F-ACCVIO
Solution:
The solution was to add a state variable so that the "users" of
the request_packets would know when it is necessary to free them
and when to assume that they have already been freed. Also
prevent possible reference to freed memory by using *request_id
instead of request_packet->request_id. And, improved telnet
symbiont process dump debug capability by sharing the BFS
runtime library and adding some debug code to the symbiont.
This enables the telnet symbiont to dump its stack into the
error log if/when the process terminates due to fatal error.
ECO B 29-NOV-1999 Alpha and VAX
Images:
TCPIP$TELNETSYM.EXE V5.0A-1B
Problem:
Forward port of fix to V5.0a caused LPD5 to depend on BFS.
Solution:
Reworked original coding of dump_stack to use the
LIB$GET_CURR_INVO_CONTEXT and LIB$GET_PREV_INVO_CONTEXT for an
alpha build. Changed to use BLISS builtins to determine which
code to use. Removed include files that are not needed. Added
more inline comments. Validate the information returned from
LIB$GET_CURR_INVO_CONTEXT; assume that LIB$GET_PREV_INVO_CONTEXT
returns the same size and version as LIB$GET_CURR_INVO_CONTEXT.
Added decode of frame type that is returned by the LIB$ routines.
Changed all calls to DUMP_STACK to TCPIP$$CALL_TRACE.
ECO C 20-DEC-1999 Alpha and VAX
Images:
TCPIP$LPD_SHR.EXE V5.0A-1C
TCPIP$LPD_SMB.EXE V5.0A-1C
TCPIP$LPD_RCV.EXE V5.0A-1C
TCPIP$LPRM.EXE V5.0A-1C
TCPIP$LPQ.EXE V5.0A-1C
Problem:
LPD can insert an unwanted linefeed at the beginning of a
VFC/PRN format text file. LPD's conversion of such files
is too literal with regard to the file's first VFC prefix.
Solution:
Suppress the unwanted linefeed if the new system logical
is defined: UCX$LPD_1ST_VFC_PREFIX_SPECIAL (UCX 4.x)
TCPIP$LPD_1ST_VFC_PREFIX_SPECIAL (TCPIP 5.x)
ECO D 22-DEC-1999 Alpha and VAX
Images:
TCPIP$LPD_SHR.EXE V5.0A-1D
TCPIP$LPD_SMB.EXE V5.0A-1D
TCPIP$LPD_RCV.EXE V5.0A-1D
TCPIP$LPRM.EXE V5.0A-1D
TCPIP$LPQ.EXE V5.0A-1D
Problem:
LPD jobs are not being relayed with SYSTEM-F-TIMEOUT
errors observed. With LPD_DEBUG = 7, log file shows
(lpd$send.c/1444) result of 'select' on socket: 3,
rfds: 0, status: 0. LPD Symbiont may also report an
ACCVIO if of recent UCX vintage (4.2 ECO 3).
Solution:
LPD was ignoring all but the minutes field in the
UCX$LPD_RETRY_INTERVAL logical. Customer had
configured a retry interval of 50 seconds -- less
than a minute, resulting in a select() timeout of 0
when waiting for remote server to acknowledge a
command.
Fixed LPD to calculate its select timeout based on
all the fields of an interval time specification,
from days down to hundreths of a second.
Also fixed ACCVIO which could occur in this situation,
a problem introduced by earlier 70-5-520 fix.
ECO E 5-APR-2000 Alpha and VAX
Images:
TCPIP$LPD_SMB.EXE V5.0A-1E
Problem:
LPD symbiont doesn't accept jobs submitted with the
/LOWERCASE qualifier.
Solution:
Modified the LPD symbiont to tell job controller we support
/LOWERCASE so jobs can be queued with this attribute.
ECO F 8-JUN-2000 Alpha and VAX
Images:
TCPIP$LPD_SHR.EXE V5.0A-1F
TCPIP$LPD_SMB.EXE V5.0A-1F
Problem:
LPD Getting extra blank lines at beginning of a report.
Solution:
Port the UCX 4.2 fix for 70-5-281 to TCP/IP V5.0A & V5.1.
Defined two logicals to control this behavior on
either a per-system basis (TCPIP$LPD_SETUP_NOLF)
or a per-queue basis (TCPIP$LPD_<queue>_SETUP_NOLF)
ECO 3 updates
--------------
ECO G 23-Oct-2000 Alpha
Images:
TCPIP$LPD_RCV.EXE V5.0A-1G
TCPIP$LPD_SHR.EXE V5.0A-1G
TCPIP$LPD_SMB.EXE V5.0A-1G
TCPIP$LPQ.EXE V5.0A-1G
TCPIP$LPRM.EXE V5.0A-1G
Problem:
Due to a build problem a TCPIP Library module did not
get built correctly causing some LPD5 images for Alpha
ECO B to be missing the latest fixes.
Solution:
The TCPIP Library was rebuilt and the LPD5 images were
relinked.
ECO H 9-NOV-2000 Alpha and VAX
Images:
TCPIP$LPD_SHR.EXE V5.0A-1H
TCPIP$LPD_SMB.EXE V5.0A-1H
Problem:
LPD queue hangs up; restarting it doesn't seem to help.
Solution:
Problem has already been fixed in UCX 4.2. Ported fixes for
QAR 30-5-311, QAR 30-5-333 and PTR 70-5-980 to V5.0A and V5.1
ECO I 30-MAR-2001 Alpha and VAX
Images:
TCPIP$TELNETSYM.EXE V5.0A-1I
Problem:
The Telnet Symbiont has a delay of 5 seconds before printing.
This delay was necessary to accomodate the DECserver 300.
A customer has requested that this delay be removed.
Solution:
Added a new logical, TCPIP$TELNETSYM_NO_DECSERVER_300 that
if defined reduces the delay from 5 seconds to a half second.
ECO K 24-APR-2001 Alpha and VAX
Images:
TCPIP$LPRSETUP.EXE V5.0A-1K
Problem:
When adding a printer via LPRSETUP, the user is allowed to enter
comments for the printer's PRINTCAP.DAT entry. However, if the
comment is longer than 77 characters, the PRINTCAP.DAT file can
be corrupted with an overlong comment line and several lines that
should be comments but aren't prefixed by the comment character
('#'). This leads to further problems when trying to delete the
corrupted entry.
Solution:
When adding a comment via LPRSETUP, automatically wrap comment
lines that are greater than 77 characters onto the next line(s).
---------------------------------------------------------------------------
Corrections for COMPAQ TCP/IP Services V5.0A MSG Images
---------------------------------------------------------------------------
ECO 1 updates
--------------
ECO A 27-SEP-1999 Alpha and VAX
Images:
UCX$SMTP_MAILSHR.EXE V5.0A-1A
UCX$MSG.EXE V5.0A-1A
Problem:
The TCPIP> ANALYZE MAIL /REPAIR operation does not fix
any inconsistencies, but exits with %TCPIP-E-SMTPERROR
and %TCPIP-W-ANA_QUEACC.
Solution:
Initialized the field passed when writing out this message
to avoid the non-printable characters. Allow the analyze mail
to continue to queue other files despite the error caused by
particular invalid files. In addition, changed the message:
TCPIP-I-ANA_NOENTR, internal consistency check error
back to the UCX 4.2 behavior to display the more informational
message:
TCPIP-I-ANA_NOENTR, no queue entry found for file <filename>
Also, added another informational message which aids in determining
which file and possible cause of the failing file message:
UCX-I-ANA_USER_RNF, $SNDJBCW(CREATE_JOB) reports RMS-E-RNF;
Suspect user name <name> is not valid for file:
<filename>
ECO B 13-JAN-2000 Alpha and VAX
Images:
TCPIP$SMTP_MAILSHR.EXE V5.0A-1C
TCPIP$SMTP_PARSESHR.EXE V5.0A-1C (VAX only)
TCPIP$SMTP_PARSESHR_TV.EXE V5.0A-1C (Alpha only)
TCPIP$SMTP_RECEIVER.EXE V5.0A-1C
TCPIP$SMTP_SFF.EXE V5.0A-1C
TCPIP$SMTP_SYMBIONT.EXE V5.0A-1C
TCPIP$MSG.EXE V5.0A-1B
Problem:
Enhancement to SMTP to provide support for 'Outbound Alias'.
Solution:
Add support for a user defined logical TCPIP$SMTP_FROM which will
be used for the text of the From: and the Return-Path:
headers. Also added support for a system manager logical
TCPIP$SMTP_PROHIBIT_USER_HEADERS which will cause the
TCPIP$SMTP_FROM logical to be ignored effectively no-oping it.
ECO C 24-MAR-2000 Alpha and VAX
Images:
TCPIP$CFS_SHR.EXE V5.0A-1A
TCPIP$MSG.EXE V5.0A-1C
Problem:
Message: cache_check detected corrupted LRU queue appears
on console after a mount from an nfs client hangs.
Solution:
Fixed miss-compare problem. Used STAT_CHE$W_CLUSTER_COUNT
instead of STAT_CHE$W_CLUSTER_LIMIT.
ECO 3 updates
--------------
ECO D 25-APR-2001 Alpha and VAX
Images:
TCPIP$FTP_CLIENT.EXE V5.0A-1F
TCPIP$FTP_CHILD.EXE V5.0A-1I
TCPIP$FTP_SERVER.EXE V5.0A-1I
TCPIP$MSG.EXE V5.0A-1D
Problem:
For file larger than 4 GB, the FTP Client incorrectly reports the
number of bytes transferred. The Kbytes/sec rate reported is also
incorrect.
Solution:
The bytes transferred count is now maintained using an extended
precision representation (64-bit long long on Alpha, two 32-bit
longword array on VAX). The Kbytes/sec rate is now calculated
using double floating-point precision.
Also took this opportunity to include an estimate of a
sequential or fixed-length file's byte length in the
"150 Opening data connection for..." message.
&n