Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
HP Services Software Patches - ucxvax_e01042
 
Modification Date:  03-JUN-98
Modification Type:  New Kit 

NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.
 
Copyright (c) Digital Equipment Corporation 1998.  All rights reserved.

PRODUCT:    DIGITAL TCP/IP Services for OpenVMS V4.2

OP/SYS:     DIGITAL OpenVMS VAX

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  UCXVAX_E01042
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  8,928 Blocks
                    Saveset A -   882 Blocks
                    Saveset B - 8,046 Blocks

     Kit Applies To:  DIGITAL TCP/IP Services for OpenVMS V4.2
                      OpenVMS VAX V6.1 and higher
     System/Cluster Reboot Necessary:  Yes
     Installation Rating:  None

     NOTE:  In order to receive the full fixes listed in this kit,
            the following remedial kits also need to be installed:

                 None 


ECO KIT SUMMARY:

An ECO kit exists for DEC TCP/IP V4.2 on OpenVMS VAX V6.1 and higher.
The following sections describe the corrections to each facility.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 INSTALL Images
---------------------------------------------------------------------------
---------------------------------------------------------------------------
ECO 1 updates:
--------------

ECO A   13-MAR-1998      Alpha and VAX

        Image:

        UCX$VERSIONS.EXE                        UCX V4.2-21A

	Sources:

	UCX$CONFIG.COM V4.2-21

	Problem:

	UCX$CONFIG does not operate in a configuration where the first
	network device configured is not the "A" controller-it assumes 
	there will always be an _EWA0:, if it is to also configure an 
	_EWB0.
	Unfortunately, this particular assumption does not hold
	true for all but one of the partitions in a Galaxy
	configuration.

	Solution:

	UCX$EDEV was updated to reflect the use of an EW-class Ethernet
	device. 

	Sources:

	UCX$SNMP_SHUTDOWN.COM V1.0-02
	UCX$SNMP_STARTUP.COM  V1.0-02

	Problem:

	There are inconsistencies in startup/shutdown of subagents.
	Also, some process names (e.g., those ending in hyphen) need 
	to be enclosed in quotation marks so as not to confuse DCL.

	Solution:

	Make sure both subagents are handled, and enclose results
	of getjpi for PRCNAM in quotes.  Also make checking of
	privileges, installation and removal of images, and
	enable/disable of service consistent between the
	procedures.

	Add P1 option to control use of privilege setting and install
	since some changes in ECO would not work with autostart 
	invocation of startup which uses non-privileged UCX$SNMP account.
	The UCX$SNMP_SHUTDOWN.COM must be run from a privileged
	account. The procedure deinstalls UCX SNMP images and disables
	the SNMP service. UCX$SNMP_STARTUP.COM runs in two modes:

	Default:
	This is the non-privileged mode in which the procedure is called
	from UCX$STARTUP.COM and for autostart from the Auxiliary server.

	Full:
	This mode is intended for interactive startup from
	a privileged account.  Use the command:
	$ @SYS$MANAGER:UCX$SNMP_STARTUP FULL.  This mode is required if
	you want to restart SNMP after running UCX$SNMP_SHUTDOWN without
	stopping and restarting UCX.

        Reference:

	Internal testing.

ECO B   3-MAR-1998      Alpha and VAX

	Problem/Solution:

	Updated UCX$BINDSETUP command procedure.
	Included UCX$NFSSETUP command procedure.

	Sources:

	UCX$NFSSETUP.COM               V4.2-21
	UCX$NFSSETUP_HELP_CLIENT.DAT   V4.2-21
	UCX$NFSSETUP_HELP_SERVER.DAT   V4.2-21
	UCX$NFSSETUP_HELP_MAIN.DAT     V4.2-21
	UCX$BINDSETUP.COM              V4.2-21
	UCX$BINDSETUP_HELP.TXT         V4.2-21

	6-MAR-1998      Alpha and VAX

	Problem/Solution:

	Prior versions of this file would complain about UCX$INET_*
	logical names being defined if network services were registered 
	before UCX$STARTUP.COM had been executed.  This is the usual 
	case at OpenVMS system startup.  This ECO allows the registration 
	of TCP/IP without such errors.
	This ECO uses the same lexical case for the host (node) name
	registration as is used in the UCX$INET_HOST and UCX$INET_DOMAIN 
	logical names. Previous versions would uppercase the fully 
	qualified host name.

	Sources:

	SYS$NET_SERVICES_UCX.COM       V4.2-21

	Problem/Solution:

	An attempt to $RCP between systems running UCX 4.1 (and 
	possibly earlier) and UCX 4.2 would fail with the error 
	%RCP-E-INVRESP.
	This error may also occur with two systems running 
	UCX 4.2 where the SYS$MANAGER:UCX$REXECD_STARTUP.COM 
	and SYS$MANAGER:UCX$RSHD_STARTUP.COM files have not 
	been copied to the appropriate directories after the 
	UCX 4.2 installation.

	PLEASE NOTE:

	The ECO installation places these two files in SYS$MANAGER:.
	To complete the solution, you must manually copy the files to
	the proper directories and ensure that file ownership and 
	protection are correct. For example (please follow local 
	security policy in setting file protections):

	$ copy SYS$MANAGER:UCX$REXECD_STARTUP.COM SYS$SYSDEVICE:[UCX$REXEC]
	$ set file/owner=parent/protection=(S:RWE,O:RWED,G:RE,W:RE) -
	  SYS$SYSDEVICE:[UCX$REXEC]UCX$REXECD_STARTUP.COM;

	$ copy SYS$MANAGER:UCX$RSHD_STARTUP.COMSYS$SYSDEVICE:[UCX$RSH]
	$ set file/owner=parent/protection=(S:RWE,O:RWED,G:RE,W:RE) -
	  SYS$SYSDEVICE:[UCX$RSH]UCX$REXECD_STARTUP.COM;

	Failure to copy both files or to properly set file 
	ownership and protection might cause RSH, REXEC, 
	and/or RCP to either fail or to act inconsistently 
	depending upon whether the /USER qualifier or proxy is used.
          
	Sources:

	UCX$REXECD_STARTUP.COM         V4.2-21
	UCX$RSHD_STARTUP.COM           V4.2-21

	Image:

        UCX$VERSIONS.EXE                        UCX V4.2-21B

        Problem/Solution:

        Corrected to display a patch version properly.

        Reference:

        Internal testing.
      
---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 Kernel Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	15-JAN-1998     Alpha and VAX

        Images:

        UCX$BGDRIVER.EXE                        UCX V4.2-21A
        UCX$INTERNET_SERVICES.EXE               UCX V4.2-21A (VAX)
        UCX$INTERNET_SERVICES_V6.EXE            UCX V4.2-21A (VAX)
        UCX$INTERNET_SERVICES_SEC.EXE           UCX V4.2-21A (VAX)
        UCX$INTERNET_SERVICES_SEC_V6.EXE        UCX V4.2-21A (VAX)
        UCX$INETACP.EXE                         UCX V4.2-21A

	Problem:

	Deassigning one channel to a particular device caused
	any pending attention ASTs to be canceled, even
	those of other channels.

	Solution:

	Flush only attention ASTs upon the final channel
	deassign operation, when the reference count drops to zero.

	References:
	CFS.52150.

ECO B  23-JAN-1998     Alpha and VAX

	Images:

        UCX$BGDRIVER.EXE                        UCX V4.2-21B
        UCX$INTERNET_SERVICES.EXE               UCX V4.2-21B (VAX)
        UCX$INTERNET_SERVICES_V6.EXE            UCX V4.2-21B (VAX)
        UCX$INTERNET_SERVICES_SEC.EXE           UCX V4.2-21B (VAX)
        UCX$INTERNET_SERVICES_SEC_V6.EXE        UCX V4.2-21B (VAX)
        UCX$INETACP.EXE                         UCX V4.2-21B

	Problem:

	IP Multicast support was compromised in V4.1 ECO W.  IGMP
	messages were no longer being sent, and the SO_BROADCAST 
	option was required in order to send Multicast datagrams.

	Solution:

	Skip several broadcast-related checks in the case
	of Multicast data. Ensure that IGMP messages are sent, and 
	that other Multicast packets are looped back upon transmit 
	for other sockets on the local host.
	Note that packets larger than the MTU are still not looped 
	back, but this should be a highly unusual case.

	References:
	CFS.53405.

ECO C  25-Feb-1998      Alpha and VAX

	Image:

        UCX$BGDRIVER.EXE                        UCX V4.2-21C
        UCX$INTERNET_SERVICES.EXE               UCX V4.2-21C (VAX)
        UCX$INTERNET_SERVICES_V6.EXE            UCX V4.2-21C (VAX)
        UCX$INTERNET_SERVICES_SEC.EXE           UCX V4.2-21C (VAX)
        UCX$INTERNET_SERVICES_SEC_V6.EXE        UCX V4.2-21C (VAX)
        UCX$INETACP.EXE                         UCX V4.2-21C

	Problems:

	1. In some circumstances, the active service counter
           was decremented below zero, resulting in an inability to
	   accept further connections.
	2. Termination AST's for created server processes were
	   missed, leading to inaccurate service counts and occasional 
	   RWMBX hangs.

		Solution:

	1. Test to avoid decrementing this counter below zero.
	2. Rather than queuing an AST each time a server process is
	   started, queue only one.  When it triggers, queue another.

        Reference:

	CFS.56956.

	Problem:

        Wrong image ID.

        Solution:

        Image was rebuilt with correct ID.

        Images:

        UCX$TRACE.EXE         UCX V4.2-21C (Alpha VMS V70 only)
	UCX$INET_ROUTING.EXE  UCX V4.2-21C (Alpha VMS V70 only)

        Reference:
           
	Internal report.

-------------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 INET Images
--------------------------------------------------------------------------------

ECO A	09-FEB-1998      Alpha and VAX

        Image:

        UCX$INETDRIVER.EXE      UCX V4.2-21A

	Problem:

	I/O cancel does not return the OpenVMS error
	SS$_CANCEL as does TGV INETDRIVER.

	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. This code should address 
	any problems with exit codes.

	References:

	None.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 IPC Images
---------------------------------------------------------------------------

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 Telnet Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A 	29-JAN-1998		Alpha and VAX

        Image:

        UCX$TNDRIVER.EXE        UCX V4.2-21A

	Problem:

	System crashed in OpenVMS routine EXE$TIMEOUT while 
	servicing a corrupt fork and wait queue.

	Solution:

	The major reason this problem occurred is that OpenVMS 
	changed the value of the name of a bit position in a TTY 
	UCB (such as a TNDRIVER UCB) in OpenVMS V6.2. In particular, 
	symbol TTY$V_FD_BUSY was defined as bit 8 in OpenVMS 
	versions prior to V6.2, and it was re-defined to be bit 10 
	in V6.2.
	The TNDRIVER distributed for all VAX platforms uses the old
	definition and for Alpha platforms running, V6.2 of OpenVMS, 
	the TNDRIVER built for V6.1 uses the old definition. The 
	result is that the wrong bit was being tested on systems 
	where the definitions were out of synch.
	The solution was to devise a new test of the condition that
	works on all platforms.

	References:

	CFS.52568.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 SNMP Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	22-JAN-1998      Alpha and VAX

        Images:

        UCX$SNMPIVP.EXE		UCX V4.2-21A

	Problem:

	Non-initialization of status variable for 
	snmp_request() routine.

	Solution:

	Initialize variable to non-error value.

	Reference:

	PTR 30-3-77.

	Images:

	UCX$OS_MIBS.EXE                         UCX V4.2-21A

	Problem:

	Display of physical address for interface group 
	(OID 1.3.6.1.2.1.2.2.1.6) incorrect:
	* First two bytes incorrect, correct bytes start 
	  at third position, but then last 2 not displayed.
	* Wrong address for display, either mismatched, 
	  or in case of LO0 address, displayed when none
	  should be (exact problem depended on the number of 
	  interfaces).

	Solution:

	Correct to string cmp routines that determined match of 
	address to interface name in table read, also copy 
	of physical address from QIO data structure to 
	application structure.

	Reference:

	PTR 30-1-571

	Problem:

	Display of incorrect next hop 
	(OID 1.3.6.1.2.14.21.1.7), often as 0.0.0.0

	Solution:

	Change to copy correct data from QIO data structure.

        Reference:

	PTR 30-2-509.

	Problem:

	In-code documentation added for unfinished Process
	Software CIDR change.

	Solution:

	Corrected.

        Reference:

	None.

	Image:

	UCX$ESNMP_SHR.EXE               UCX V4.2-21A

	Problem:

	A shridmismat error for applications linked with
	the previous version of the ucx$esnmp_shr.exe.

	Solution:

	Insert GSMATCH=lequal,a,b into options file, where
	a,b match the values inserted by the linker for the
	base version of UCX V4.1.

        Reference:

	None.

	Images:

	UCX$ESNMP_SHR.EXE                       UCX V4.2-21A

	Problem:

	Function missing from shareable image for API: inst2ip().

	Solution:

	For Alpha: add SYMBOL_VECTOR to link options file.
	For VAX: add VECTOR to macro file.

        Reference:

	None.

	Problem:

	Header file corrections:
	esnmp.h: need #define for __() so users can use this
		 header file for custom applications.
	ioctl.h: minor correction taken from old UCX V4.1 code
		 for consistency.

	Solution:

	esnmp.h: with #ifdef __VMS, insert #define __(x) x.
	ioctl.h: edit out old structure value (rt_mask) not
	         used in OpenVMS.

	Reference:

	None.

ECO B   17-FEB-1998      Alpha and VAX

        Image:

        UCX$ESNMP_SERVER.EXE         UCX V4.2-21B
        SYS$SYSTEM:UCX$OS_MIBS.EXE   UCX V4.2-21B
        SYS$SYSTEM:UCX$HR_MIB.EXE    UCX V4.2-21B

	Problem:

	Incorrect MIB variable reporting, counts for if group.

	Solution:

	Aligned header file.

        Reference:

	PTR 30-2-377

	Problem:

	MIB-II subagent aborts if system has pseudo-interface
	configured.

	Solution:

	Correct clearing out of buffer area.
	Also, include interface name in error message for easier
	debugging.

	Reference:

	PTR 30-1-688.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 SDA Images
---------------------------------------------------------------------------
              
---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 Finger Images
---------------------------------------------------------------------------

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 BIND Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	19-DEC-1997      Alpha and VAX

        Images:

	UCX$ACCESS_SHR.EXE	UCX V4.2-21A

	Problem:

	Obsolete IQUERY calls need to be removed for 
	compatibility with other BIND implementations.

	Solution:

	Replaced the call to FindHostInfo that uses IQUERY
	with GetHostByAddr().
        
        Reference:   

	None.

	Images:

	UCX$METRIC.EXE          UCX V4.2-21A (Alpha VMS V70)

	Problem:

	Wrong image ID.

        Solution:

        Image was rebuilt with correct ID.

        Reference:

	Internal report.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 BIND_SERVER Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	13-JAN-1998      Alpha and VAX

        Image:

	UCX$BIND_SERVER.EXE	UCX V4.2-21A

	Problem:

	The name server generated too much logging information about
	load balancing.

	Solution:

	Put both syslog() calls inside "if DEBUG" clause.

	Reference:

	PTR 30-1-630

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 PWIP Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	22-JAN-1998      Alpha and VAX

        Image:

        UCX$PWIPACP.EXE          UCX V4.2-21A

	Problem:

	Several different symptoms, including crashes, 
	memory corruption, loss of PWIP connections, etc.

	Solution:

	A variable in routine, getChan(), was incorrectly 
	declared to be static. The result was that, 
	if the routine was ever entered simultaneously
	(such as in normal mode and in an AST), data could be 
	corrupted. This day-one bug was dormant until the latest 
	release of PATHWORKS. With an older version of PATHWORKS,  
	conditions were such that the routine was never entered 
	simultaneously.  However, the new release has a different 
	set of calls into PWIP and the bug is now exposed.  The
	solution was to make the variable a normal automatic variable.

	Reference:

	Many reports.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 UCP Images
---------------------------------------------------------------------------
ECO A   06-APR-1997 Alpha only.

        Images:

        UCX$UCP.EXE          UCX V4.2-21A (Alpha VMS V70)

        Problem:

        Wrong image ID.

        Solution:

        Image was rebuilt with correct ID.

        Reference:

        Internal report.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 BOOTP and TFTP Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A 	04-FEB-1998             Alpha and VAX

        Image:

	UCX$BOOTP.EXE		UCX V4.2-21A

	Problems:

	BOOTP replies with the wrong Server Address on a
	multiple interface host.

	Solutions:

	Correct a problem in the subnet_match() routine. Pass subnet
	mask of the BOOTP client to subnet_match(). The responding
	interface must be in the same subnet as BOOTP client.

	References:

	CFS.54174.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 FTP Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	05-FEB-1998     Alpha and VAX

        Image:

        UCX$FTP.EXE             UCX V4.2-21A

	Problem:

	The FTP initialization file, FTPINIT.INI, was not being
	used when FTP executed in batch mode.

	Solution:

	Corrected the code path to place the FTP initialization 
	into the common path independent of whether the FTP client 
	is executing on a DC$_TERM or not.

	Reference:

	PTR 30-1-605, CFS.55947.

ECO D   05-FEB-1998     Alpha and VAX

        Image:

        UCX$FTP.EXE             UCX V4.2-21D

	Problem:

	Internal problems caused by the presence of the
	FTPINIT.INI file.  The DCL command line was lost
	if the file existed.

	Solution:

	Processed the initialization file only after 
	parsing the command line.

	Reference:

	Internal testing.

ECO E	05-FEB-1998     Alpha and VAX

        Image:

        UCX$FTP.EXE             UCX V4.2-21E

	Problem:

	If the local source file of the COPY/FTP command
	does not exist (or an error signaled), that error
	was not returned to DCL for examination of $STATUS.

	Solution:

	The status FTP$_NORMAL was always returned by the
	central FTP PUT routine, even after it signals the error.
	In addition, the routine did not signal the error in 
	typical FTP fashion.
	The code has been modified to signal an appropriate
	error and to return an error indication to DCL.
                                          
	Reference:

	PTR 30-1-618, CFS.56104.

ECO F	09-FEB-1998     Alpha and VAX

        Image:

        UCX$FTP.EXE		UCX V4.2-21F

	Problem:

	The PUT command send an unwildcarded file in its
	uppercase OpenVMS format, which is not acceptable for UNIX
	systems.

	Solution:

	When the responsibility for uppercasing moved to the
	caller of the common 'put' routine, the appropriate
	code needed in the unwildcarded put routine was
	never implemented.  The file's name from the NAM
	block is now lowercased if the connection is not in
	VMS-Plus mode and uppercase enforcement is disabled.
             
	Reference:

	CFS.55993 (PTR 30-1-609).

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 FTPD Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	29-JAN-1998      Alpha and VAX

        Image:

        UCX$FTPC.EXE        UCX V4.2-21A

	Problem:

	CWD only reported syntax errors when attempting to
	establish a new default directory even though the
	device and/or directory strings may be invalid.

	Solution:

	The $PARSE SYNCH option was being used when parsing
	the new default directory.  Turning this off allows
	the device and directory strings to be checked for
	validity and existence.

	Reference:

	PTR 30-1-549.

ECO B   30-JAN-1998      Alpha and VAX

        Image:

        UCX$FTPC.EXE        UCX V4.2-21B

	Problem:

	The command 'CWD /' returns an error.

	Solution:

	Treat 'CWD /' as synonymous with 'CWD ~' and 'CWD':
	set the default to SYS$LOGIN:.
	Reference:

	CFS.56290.

ECO C   05-FEB-1998       Alpha and VAX

        Image:

        UCX$FTPC.EXE        UCX V4.2-21C

	Problem:

	RENAME does not handle wildcard characters correctly.

	Solution:

	Recoded RNTO action routine to handle wildcards
	as well as multiline output.

	Problem:

	CWD does not handle logical names properly when they
	are expressed without a colon (:) at the end.

	Solution:
	Added a check for a logical name when deciding if the 
	string needs to be translated from UNIX to OpenVMS format.

        Reference:

	CFS.54606, PTR 30-1-523.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 CFS_SHR Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	16-FEB-1998     Alpha only

        Images:

        UCX$CFS_SHR.EXE         UCX V4.2-21A

	Problem:

	On Alpha, if two threads enter the BFS$$SIGNAL routine,
	they can be merged together.  This condition can lead 
	to an assortment of symptoms, including an ACCVIO message, 
	a corrupted stack, SS$_OPCDEC, and looping on thread 
	rundown trying to unlock a resource not owned by this thread.

	Solution:

	Initialize the stored ATCB pointer for
	Alpha-conditionalized code as well as VAX code.

	Reference:

	CFS.45425, CFS.50080.

	Problem:

	On Alpha systems, file system error messages go to
	UCX$CFS_FATAL_MESSAGES, by default assigned to _OPA0:, 
	instead of being handled as OPCOM messages as with VAX 
	systems.  Writing directly to _OPA0: can be annoying on 
	workstation servers, because the writing causes the 
	monitor to display the console window.  

	Solution:

	The executive mode stack must be switched back to normal 
	before the $SNDOPR is done.

	Reference:

	CFS.41421, UCX 4724.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 DNFS Images
---------------------------------------------------------------------------
ECO A   06-APR-1997 Alpha only.

	Images:

        UCX$DNFSACP.EXE         UCX V4.2-21A (Alpha VMS V70)
        UCX$DNFSDISMOUNT.EXE    UCX V4.2-21A (Alpha VMS V70)
        UCX$DNFSDRIVER.EXE      UCX V4.2-21A (Alpha VMS V70)
        UCX$DNFSMOUNT.EXE       UCX V4.2-21A (Alpha VMS V70)

	Problem:

	Wrong images IDs.

	Solution:

	Images were rebuilt with correct IDs.
         
	Reference:

	Internal report.
         
---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 LPD Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	22-JAN-1998      Alpha and VAX

        Images:

        UCX$LPD_SHR.EXE              UCX V4.2-21A

	Problem:

	Unable to print 700 small or medium ANSI or 
	binary files at once.

	Solution:

	Modified card_RMS() function, which on buffer 
	overflow calls flush_card() rather than signaling
	RMS$_RTB.
	Reference:

	CFS.52472.

	Problem:

	Unable to stop and delete queues in a processing state.
	It appears that the issue was one of not recognizing and 
	closing "damaged" connections, and therefore remained 
	"stuck" down in the driver and unable to respond to SMB 
	messages and the like.

	Solution:

	Added code in rresvport() to use system logical names
	UCX$LPD_KEEPALIVE (y/n), UCX$LPD_PROBETIME (1..64k) and
	UCX$LPD_DROPTIME (1..64k).

        Reference:

	CFS.51291.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 POP Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	26-JAN-1998      Alpha and VAX

        Images:

        UCX$POP_SERVER.EXE              UCX V4.2-21A

	Problem:

	The POP server could not process mail messages with more
	than 255 bytes in a line.

	Solution:
	Changed code to bypass the limit by looking at OpenVMS
	callable mail's internal buffer for the message.

	Problem:
	When trying to read large mail messages, the POP
	server hangs and issues a MAIL-W-NOMOREREC error message 
	to the log file.

	Solution: 

	The problem occurs because OpenVMS
	callable mail reads the entire mail message.
	If the process does not have enough memory,
	callable mail returns MAIL-W-NOMOREREC.
	  
	The solution is to detect this condition and
	send a mail message back to the recipient telling
	to asking the system administrator to increase the 
	POP server account's page file quota, thereby 
	correcting the problem.

        Reference:

	PTR 30-1-600, 30-1-614.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 SMTP Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A   26-JAN-1998      Alpha and VAX

        Image:

	UCX$SMTP_MAILSHR.EXE            UCX V4.2-21A
        UCX$SMTP_RECEIVER.EXE           UCX V4.2-21A
        UCX$SMTP_SYMBIONT.EXE           UCX V4.2-21A
        UCX$SMTP_PARSESHR.EXE (VAX)     UCX V4.2-21A
	UCX$SMTP_PARSESHR_TV.EXE (Alpha)UCX V4.2-21A
        UCX$UUENCODE.EXE                UCX V4.2-21A
        UCX$UUDECODE.EXE                UCX V4.2-21A
	UCX$SMTP_SFF.EXE                UCX V4.2-21A

	Problem:

	A customer tried to send file that had fixed-length 
	records, which caused various problems.

	Solution:

	This situation is not supported. Print warning when
	action is attempted.

        Reference:

	PTR: 30-1-529, CFS.54722.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 RSH Images
---------------------------------------------------------------------------

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 RLOGIN Images
---------------------------------------------------------------------------
ECO A   06-APR-1997 Alpha only.

        Images:

	UCX$RLOGIN.EXE          UCX V4.2-21A (Alpha VMS V70)
        
	Problem:

        Wrong image ID.

	Solution:

        Image was rebuilt with correct ID.

	Reference:

	Internal report.                

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 RPC Images
---------------------------------------------------------------------------
ECO 1 updates:
--------------
ECO A	29-JAN-1998      Alpha and VAX

        Images:

        UCX$RPCXDR_SHR.EXE      UCX V4.2-21A

	Problem:

	IEEE double precision results in 'Server can't
	decode argument' from a UCX client.

	Solution:

	The RPC message appears to be short by four bytes.
	Checking the source revealed that if the first four
	bytes encode properly, the second four bytes will 
	not be encoded because an || was being used instead 
	of an && condition.

	References:

	PTR 30-1-629.

---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 RCP Images
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Corrections for DIGITAL TCP/IP Services V4.2 NTP Image
---------------------------------------------------------------------------


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. 

	Postinstallation Notes.

	To complete the installation, do the following:

	1.	Copy SYS$MANAGER:UCX$RSHD_STARTUP.COM to 
		SYS$SYSDEVICE:[UCX$RSH].

	2.	Copy SYS$COMMON:[SYSMGR]UCX$SNMP_SHUTDOWN.COM to
		SYS$SYSDEVICE:[UCX$SNMP]UCX$SNMP_SHUTDOWN.COM.

	3.	Copy SYS$COMMON:[SYSMGR]UCX$SNMP_STARTUP.COM to
Files on this server are as follows:
Files on this server are as follows:
»ucxvax_e01042.README
»ucxvax_e01042.CHKSUM
»ucxvax_e01042.CVRLET_TXT
»ucxvax_e01042.a-dcx_vaxexe
»ucxvax_e01042.b-dcx_vaxexe
privacy statement using this site means you accept its terms